Re: new plugin: alphabetical index

I see your point, of course. PyBloxsom needs a default caching flag
mechanism. E.g., "this entry has changed!" flag. Should be "simple" to
add (not that I am volunteering at the point) mtime and filesize is
good enough for rsync (and when something apparently changes, an
md5sum - at least that is how I remember it works). An aside: file
stats are pretty dirt cheap, even for a lot of files.

-todd

On 10/9/06, Ryan Barrett <pyblosxom-6sb6M7qyT/[email protected]> wrote:
> On Mon, 9 Oct 2006, Todd Warner wrote:
>
> > Nifty. But it indexes by *filename* not by title of entry, so... for
> > me, not so useful to me. If you could have it index by actual entry
> > title that would be better and really makes more sense.
>
> true! the problem is, it would have to open and read the first line of *every
> entry* on each request. it already has to stat every entry, which i'm allergic
> to as is. reading every one would be way worse.
>
> still, from a functionality point of view, it is the right thing to do.
>
> currently, a cb_walk() callback, which plugins would implement to cache the
> entry hierarchy semi-permanently, is at the top of my pyblosxom todo list.
> once i've done that, i'll think about how to index by title efficiently.
>
> (granted, people with fastcgi or wsgi or mod_python don't have to worry as
> much minimizing file stats and reads. i'm jealous of them. :P)
>
> -Ryan
>
> --
> http://snarfed.org/
>
>

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV