Using non-ORM bindings

[fancyremarker]

I'm using Garner in a project (really, a couple projects) where we don't ever need to bind to ActiveRecord or Mongoid objects. Instead, we want to cache certain data (the roles to which a user belongs) and bind it to the OAuth token they present.

Right now, I'm doing this by monkey-patching the AccessToken class in an initializer:

Garner.configure do |config|
  # Other configuration options...
  config.binding_key_strategy = Garner::Strategies::Binding::Key::CacheKey
end

module Fridge
  class AccessToken
    include Garner::Cache::Binding

    def cache_key
      id
    end
  end
end

Then I can do stuff like:

garner.bind(token) { roles.map(&:href) }

What do we think is the appropriate way to "Garner-ify" non-ORM objects? Is re-opening the class the right way to do this? Right now, it's necessary to, at a minimum include Garner::Cache::Binding in any class whose instances will be used as bindings. Is there a better way?

[dblock]

Reopening is probably fine, except I think I would like to write something like Fridge::AccessToken.extend Garner::Cache::Binding::GenericBindingById. Maybe there's a way to delegate this, too?

config.something = {
    Fridge::AccessToken => ...
}

This could allow delegating Object's binding.