Sha256: d032e760d03fca6a55a73600a97afd10b6d720258d3ef6683f268e6c126be76d
Contents?: true
Size: 1.19 KB
Versions: 1
Compression:
Stored size: 1.19 KB
Contents
# Morlock Morlock turns your memcached server into a distributed, conflict-eating machine. Rails integration is dug in. ## Usage ### Creating a new Morlock instance #### Ruby require 'memcache-client' require 'morlock' mem_cache_client = MemCache.new("memcached.you.com") morlock = Morlock.new(mem_cache_client) If you prefer Dalli, use that instead: require 'dalli' dc = Dalli::Client.new('localhost:11211') morlock = Morlock.new(dc) #### Rails If you're already using MemCacheStore in your Rails app, using Morlock is trivial. Morlock will automatically use the memcached server that is backing Rails.cache. With Bundler: gem 'morlock', :require => 'morlock/rails' Or in any script after Rails has loaded: require 'morlock/rails' At this point, `Rails.morlock` should be defined and available. Use it instead of `morlock` in the examples below. ### Distributed Locking Possible usages: handle_failed_lock unless morlock.lock(key) do # We have the lock end morlock.lock(key) { # We have the lock } || raise "Unable to lock!" morlock.lock(key, :failure => failure_proc) do # We have the lock end morlock.lock(key, :failure => failure_proc, :success => success_proc)
Version data entries
1 entries across 1 versions & 1 rubygems
Version | Path |
---|---|
morlock-0.0.1 | README.markdown |