Interlock 1.4

Interlock is an intelligent fragment cache for Rails. It works by making your view fragments and associated controller blocks march along together. If a fragment is fresh, the controller behavior wont run.
This eliminates duplicate effort from your request cycle. Your controller blocks run so infrequently that you can use regular ActiveRecord finders and not worry about object caching at all.
Invalidations are automatically tracked based on the model lifecyle, and you can scope any block to an arbitrary level. Interlock also caches content_for calls, unlike regular Rails, and can optionally cache simple finders.
Interlock is using a tiered caching layer so that the multiple look-ups of a key only hit memcached once per request.

System requirements:
- memcached
- memcache-client
- Rails 2.1

Enhancements:
- Rails 2.1 compatibility. Store dependency trees per object, when possible. Use shorter namespaces for Memcached.