Bric::App::Cache - Object for managing Application-wide global data.
$Revision: 1.14 $
$Date: 2002/08/30 22:13:38 $
use Bric::App::Cache;
my $c = Bric::App::Cache->new;
$c = $c->set($key, $val);
my $val = $c->get($key);
my $time = $c->get_lmu_time;
$c = $c->set_lmu_time;
This module provides a cache object to cache data that needs to persist across all processes and across all requests, through time and space. The cache is cleared on server restart - for more permenant storage see Bric::Util::DBI.
A Bric::App::Cache object is available from Mason components in the global variable $c.
This module is implemented as a two-level cache in order to provide the best possible performance.
The first level is provided by Cache::Mmap. Cache::Mmap is a very fast, shared, file-based cache. However, it is also a fixed-size cache that will drop items from the cache when the cache becomes full or the item to be stored is too large.
When an object cannot be stored in the first-level cache it is passed to the second-level. The second-level cache (also known as a backing store) is provided by Cache::Cache. Cache::Cache is quite a bit slower than Cache::Mmap but has the advantage of being variable-sized. As such it grows dynamically and won't refuse to store an object unless it runs out of disk space.
The get() procedure is:
Look in first-level cache for item. If found, return it and finish.
Look in second-level cache for item. If found, return it and finish.
Note in first-level cache that item is not in second-level cache. This will prevent a look in the second-level cache on the next request for this item.
And the set() prodedure is:
Try to set the item in the first-level cache. If success, finish. If fail, delete old item if it exists.
Set the item in the second-level cache. This must succeed or a fatal error will result.
NOTE: Under QA_MODE all set()s are sent to the secondary-cache to allow the cache to be debugged. Cache::Mmap lacks the ability to list all keys in the cache which is used by the QA_MODE code.
Instantiates a Bric::App::Cache object. No initial values may be passed.
Throws:
Unable to instantiate cache.
Side Effects: NONE.
Notes: NONE.
Not implemented - not needed.
Throws:
Bric::App::Cache::lookup() method not implemented.
Side Effects: NONE.
Notes: NONE.
Not implemented - not needed.
Throws:
Bric::App::Cache::list() method not implemented.
Side Effects: NONE.
Notes: NONE.
Dummy method to prevent wasting time trying to AUTOLOAD DESTROY.
Throws: NONE.
Side Effects: NONE.
Notes: NONE.
Not implemented - not needed.
Throws:
Bric::App::Cache::list_ids() method not implemented.
Side Effects: NONE.
Notes: NONE.
Clears the cache of all stored data.
Throws: NONE.
Side Effects: NONE.
Notes: NONE.
Returns a value for the specified key. Call $c->set($key, $value) to store a value.
Throws:
Unable to fetch value from the cache.
Side Effects: NONE.
Notes: NONE.
Stores $value as referenced by $key. Call $c->get($key) to retrieve $value.
Throws:
Unable to cache value.
Side Effects: NONE.
Notes: NONE.
Returns the epoch time when a user object was last modified.
Throws:
Unable to fetch value from the cache.
Side Effects: NONE.
Notes: NONE.
Sets the epoch time when a user object was last modified.
Throws:
Unable to cache value.
Side Effects: NONE.
Notes: NONE.
NONE.
NONE.
Reads a value from the backing store. See the IMPLEMENTATION section avove for details.
Throws:
Unable to fetch value from the backing cache.
Side Effects: NONE.
Notes: NONE.
Writes a value to the backing store. See the IMPLEMENTATION section avove for details.
Throws:
Unable to cache value in the backing cache.
Side Effects: NONE.
Notes: NONE.
NONE.
David Wheeler <david@wheeler.net>
Sam Tregar <stregar@about-inc.com>
Bric, Bric::App::Session, Apache::Session
Hey! The above document had some coding errors, which are explained below:
=back doesn't take any parameters, but you said =back 4
=back doesn't take any parameters, but you said =back 4