Larry Leszczynski wrote:
But I see your point about the danger of
clearing/flushing more than you might expect. Regardless of cache
flavor, you could set up separate backend instances for different pools
of data (via e.g. different cache_roots for Cache::FileCache or
different server instances
Does it make sense to add a clear() method to Catalyst::Plugin::Cache,
in addition to the existing get(), set() and remove()? It seems like a
common action for cache manipulation.
Any of the various Cache::Cache-based backend flavors should be able to
support it out of the box. For specific
On Mar 6, 2009, at 7:42 PM, Larry Leszczynski wrote:
Does it make sense to add a clear() method to Catalyst::Plugin::Cache,
in addition to the existing get(), set() and remove()? It seems
like a
common action for cache manipulation.
Any of the various Cache::Cache-based backend flavors
On Fri, 06 Mar 2009 20:11 -0500, Jason Kohles em...@jasonkohles.com
wrote:
On Mar 6, 2009, at 7:42 PM, Larry Leszczynski wrote:
Does it make sense to add a clear() method to Catalyst::Plugin::Cache,
in addition to the existing get(), set() and remove()? It seems
like a
common action
