Skip to content


Subversion checkout URL

You can clone with
Download ZIP
branch: master

This branch is 47 commits ahead of ecin:master

Failed to load latest commit information.
lib Release 0.7.0.
spec No need for defaults spec. All explicitly spec'd in shared adapter.
.gitignore Remove lock file from repo
.rspec Auto add color to rspec
.travis.yml No more 1.9.2. Big changes for 0.7. All chronicled in changelog.
Gemfile Missing gem in gemfile
Guardfile Just run all specs when things change.
LICENSE Minor: formatting. Big changes for 0.7. All chronicled in changelog.
Rakefile Switch to bundler/gem_tasks require in gemfile.
adapter.gemspec Update gemspec.


A simple interface to anything.

Defining an Adapter

An adapter requires 4 methods to work: read, write, delete and clear.

Adapter.define(:memory) do
  def read(key, options = nil)

  def write(key, attributes, options = nil)
    client[key] = attributes

  def delete(key, options = nil)

  def clear(options = nil)

Note: in order for things to be most flexible, always wrap key with key_for(key) which will ensure that pretty much anything can be a key. Also, by default encode and decode are included and they Marshal.dump and Marshal.load. Feel free to override these if you prefer JSON serialization or something else.

Once you have defined an adapter, you can get a class of that adapter like this:


This returns a dynamic class with your adapting methods included and an initialize method that takes a client. This means you can get an instance of the adapter by using new and passing the client (in this instance a boring hash):

adapter = Adapter[:memory].new({}) # sets {} to client
adapter.write('foo', 'bar')'foo') # 'bar'
adapter.fetch('foo', 'bar') # returns bar and sets foo to bar

Note: You can also optionally provide a lock method. Read More

Adapter Power User Guides

Mailing List!forum/toystoreadapter

Note on Patches/Pull Requests

  • Fork the project.
  • Make your feature addition or bug fix in a topic branch.
  • Add tests for it. This is important so we don't break it in a future version unintentionally.
  • Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine, but bump version in a commit by itself so we can ignore when we pull)
  • Send a pull request.
Something went wrong with that request. Please try again.