Re: Patch for simple walk caching

> >Also, as Wari said, permalinks don't even benefit from caching much.
> >The question is how to determine that something is a permalink - I
> >think I'll just set the cache up to ignore filelists with only one
> >entry.
> >
> Hey, Bill, let me retract that. Caching really just keeps data about the
> entry. Permalinks may contain comments, which are not really part of the
> pyblosxom caching system. Pyblosxom caches entries, and comments are
> just extensions to the entry, but does not touch it. What I was trying
> to say was, permalink/single entry pages does not benefit by being
> statically generated (that is, output is a physical file) if the
> comments plugins is in use. In most cases, only a file update
> invalidates the entry cache, and re-reads the entry from there. Comments
> does not update the entries in anyway.
> 
> If an entry is a word DOC file, and a DOC_reader plugin is used to read
> the entry, and say it costs about 10-20 seconds to read the DOC file and
> to render to the appropiate HTML, then save to the entry_cache, the
> subsequent reads would then costs 10 miliseconds (this is all
> hypothetical of course:).  That Bill, is why one wants a cache, even for
> permalinks.
> 

I agree 100% ... I figured that out while talking with Will. I think I
knew I why I did it when I started writing the cache, and then got so
wrapped up in the writing that I forgot.

Peace
Bill Mill
bill.mill at gmail.com


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/