Re: pyblosxom 2.0: entry level caching

On 8/29/07, Asheesh Laroia <[email protected]> wrote:
> On Tue, 28 Aug 2007, Will Guaraldi wrote:
> > * ``entrycache_get`` -
> >  This retrieves items from the cache given an entryid.  Since this is a
> >  callback, if one entry cache handling plugin can't handle the request,
> >  it gets passed on to another.  This would allow for multiple levels of
> >  caching.
> >
> > * ``entrycache_update`` -
> >  This updates items in the cache given an entryid.  Since this is a callback,
> >  **all** entry cache handling plugins are notified of the update.
>
> How would cache expiry work?  If I update a file, I guess entrycache_get()
> would notice that the mtime is newer, so it would return None, and
> then after render time the Pyblosxom core would call all the
> entrycache_update() functions?

That's a possibility.  For every entry we'd call entrycache_get and
entrycache_update regardless of whether the entrycache_get returned
None or not.

Are there other scenarios that we need to think about?

/will

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/