Re: Funky caching
Jesse Lawrence <lawrence_jesse-FFYn/[email protected]>
| Newsgroups | gmane.comp.web.pyblosxom.devel |
|---|---|
| Message-ID | <[email protected]> |
will guaraldi wrote: > On Wed, 8 Dec 2004, Jesse Lawrence wrote: > >> >> I am working on Roberto De Almeida's funky caching implementation in >> an attempt to fully integrate it with pyblosxom, handling newly >> posted comments and all. It is my opinion (for what it's worth) that >> this should be the one and only static rendering mechanism for >> pyblosxom, because it's automatic (behind the scenes) and fairly >> elegant. > > > I'm a little puzzled... what do you mean by "one and only static > rendering mechanism"? > > /will > I mean that funky caching just happens, much like the original (at least I thought) idea of Pyblosxom (Blosxom); you place a file in a directory, and it becomes a blog post. It just happens. To me, the current static rendering method (no offense) is contrary to the idea behind Pyblosxom. Having to run a script after making a new post adds to the effort of posting. Jesse > > ------------------------------------------------------- > 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/ > _______________________________________________ > Pyblosxom-devel mailing list > Pyblosxom-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org > https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel > ------------------------------------------------------- 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/