Results for simple-http-adapter

A simple & very fast S3 client supporting sync / async HTTP adapters

A JRuby adaption and gem packaging of the {Simple Logging Facade for Java}[http://www.slf4j.org/]. Provides all jar dependencies and a Ruby Logger compatible facade. SLF4J is a java logging abstraction and set of adapters to various concrete logging implementations and legacy logging APIs. The slf4j gem adds a ruby core Logger compatible facade to SLF4J, and makes any needed adapters available to JRuby applications. This makes it possible to unify and control logging output of both java and ruby components in a JRuby application.

A simple & very fast S3 client supporting sync / async HTTP adapters

This project aims to replace the builtin git-http-backend CGI handler distributed with C Git with a Rack application. By default, Grack uses calls to git on the system to implement Smart HTTP. Since the git-http-backend is really just a simple wrapper for the upload-pack and receive-pack processes with the '--stateless-rpc' option, this does not actually re-implement very much. However, it is possible to use a different backend by specifying a different Adapter.

A very simple naive Bayesian classifier. I'm just using it as practice as I learn how to package ruby code. The algorithm used here is not original, but an adaptation from Burak Kanber's Machine Learning in Javascript series. http://readable.cc/feed/view/34236/burak-kanber-s-blog

Diff and patch tables

This is a Compass Plugin that utilizies the Unsemantic CSS Framework (http://unsemantic.com/) by Nathan Smith. This plugin is very simple way to allow people to create a Grid system for websites using the unsemantic-vars.sass file within the sass/partials folder. This does not include the adapt version. This is only for the responsive version of the framework. I have duplicated the code from sass/partials/unsemantic-vars.sass file to the main .sass file for the compass plugin so it will be easier to implement the @import. Instead of @import "compass-unsemantic/unsemantic-vars" people can just write @import "compass-unsemantic" at the appropriate places. This plugin is mainly meant for people who want to roll their own grid using the Unsemantic CSS Framework (http://unsemnatic.com/). For documentation on where to add these import statements refer to http://unsemantic.com/sass-documentation#14-roll-your-own.

Stockpile is a simple key-value store connection manager framework. Stockpile itself does not implement a connection manager, but places expectations for implemented connection managers. So far, only Redis has been implemented (stockpile-redis). Stockpile also provides an adapter so that its functionality can be accessed from within a module. Release 2.0 fixes an issue when Stockpile options are provided with an OpenStruct, originally reported as {stockpile-redis#1}[https://github.com/halostatue/stockpile-redis/issues/1]. Support for Ruby 1.9 has been dropped.

Diff and patch tables

Contentful API wrapper library exposing an ActiveRecord-like interface

==== Topic Maps for Rails (rtm-rails) RTM-Rails is the Rails-Adapter for Ruby Topic Maps. It allows simple configuration of topicmaps in config/topicmaps.yml. ==== Overview From a developer's perspective, RTM is a schema-less database management system. The Topic Maps standard (described below) on which RTM is based provides a way of creating a self-describing schema just by using it. You can use RTM as a complement data storage to ActiveRecord in your Rails apps. ==== Quickstart - existing Rails project jruby script/generate topicmaps Run the command above after installing rtm-rails. This will create * a minimal default configuration: config/topicmaps.yml and * a file with more examples and explanations config/topicmaps.example.yml * a file README.topicmaps.txt which contains more information how to use it and where to find more information * an initializer to load the topicmaps at startup * a rake task to migrate the topic maps backends in your rails application. ==== Quickstart - new Rails project For a new Rails application these are the complete initial steps: jruby -S rails my_topicmaps_app cd my_topicmaps_app jruby -S script/generate jdbc jruby -S script/generate topicmaps # The following lines are necessary because Rails does not have a template # for the H2 database and Ontopia does not support the Rails default SQLite3. sed -e "s/sqlite3/h2/" config/database.yml > config/database.yml.h2 mv config/database.yml.h2 config/database.yml # Prepare the database and then check if all is OK jruby -S rake topicmaps:migrate_backends jruby -S rake topicmaps:check ==== Usage inside the application When everything is fine, let's create our first topic: jruby -S script/console TM[:example].get!("http://example.org/my/first/topic") # and save the topic map TM[:example].commit Access the configured topic maps anywhere in your application like this: TM[:example] To retrieve all topics, you can do TM[:example].topics To retrieve a specific topic by its subject identifier: TM[:example].get("http://example.org/my/topic") Commit the changes to the database permanently: TM[:example].commit ... or abort the transaction: TM[:example].abort More information can be found on http://rtm.topicmapslab.de/ ==== Minimal configuration default: topicmaps: example: http://rtm.topicmapslab.de/example1/ The minimal configuration creates a single topic map, named :example with the locator given. This topic map will be persisted in the same database as your ActiveRecord connection if not specified otherwise. The default backend is OntopiaRDBMS (from the rtm-ontopia gem). A more complete configuration can be found in config/topicmaps.example.yml after running "jruby script/generate topicmaps". It also includes how to specifiy multiple connections to different data stores and so on. ==== Topic Maps Topic Maps is an international industry standard (ISO13250) for interchangeably representing information about the structure of information resources used to define topics, and the relationships between topics. A set of one or more interrelated documents that employs the notation defined by this International Standard is called a topic map. A topic map defines a multidimensional topic space - a space in which the locations are topics, and in which the distances between topics are measurable in terms of the number of intervening topics which must be visited in order to get from one topic to another, and the kinds of relationships that define the path from one topic to another, if any, through the intervening topics, if any. In addition, information objects can have properties, as well as values for those properties, assigned to them. The Topic Maps Data Model which is used in this implementation can be found on http://www.isotopicmaps.org/sam/sam-model/. ==== License Copyright 2009 Topic Maps Lab, University of Leipzig. Apache License, Version 2.0

No description provided.