Re: Patch for simple walk caching

Uh...  all the static rendering is built-in to the PyBlosxom core.  There 
are two methods in the tools module: update_static_entry and render_url. 
These two allow plugins to re-render statically rendered pages based on 
the entry involved.  They already handle updating date pages and index 
pages and allow the user to specify additional urls that need to be 
re-rendered whenever a page is updated.

That's the infrastructure that we needed to allow the comments plugin to 
re-render pages after a comment is added.  I tried to cover the case where 
xml_rpc plugins created or updated an entry--the static rendering stuff 
should handle that as well (but as far as I know it doesn't yet).

That should cover what you're calling "invalidate_cache".

It should do so automatically and additionally it only does it when things 
change rather than every 30 minutes.

/will


On Tue, 7 Dec 2004, Bill Mill wrote:
>
> sure there is; I don't have to worry about it. If I render my website
> statically, I have to upload it to my webserver every time I change
> something. Now, I could write a cron script to do that every so often
> and get a similar effect, but I don't know if my laptop's on, or
> online, or in windows, or ...
>
> Furthermore, we have the possibility of making it truly dynamic with
> an invalidate_cache call (or some way I haven't thought of yet) as I
> started discussing with Ted. If we can get that working, we can skip
> the parsing of the entries when nothing's changed, and really limit
> the parsing to when a file is changed.
>
> 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/