Smarter cache invalidation

[jpodwys]

Let's say I have a basic CRUD journal site--I can create an entry, edit/delete an entry, view an entry, and view a list of entries. Cache invalidation works great when I delete or update an entry. However, there is no way to automatically tell the entry list cache key to invalidate when a CRUD action happens to a single entry.

I need to add some way of associating keys so that when a single entry, for example, is modified, the cache key for the entry list is invalidated.

[jpodwys]

I think I can accomplish this by allowing users to add a prefix to the generated cache key via a chainable. However, this requires updates to all cache modules to handle deletions of keys that start with a given string.

[jpodwys]

It also assumes the cache modules can do wild-card deletions efficiently.