Re: filestat

Option 1 doesn't prevent people from writing a filestat plugin that pulls
from an index file.

Option 1 also doesn't cause PyBlosxom to open and read every file in your
datadir unless you have a plugin (such as one that pulls the mtime from
the file data) that requests PyBlosxom to do so.

So I think option 1 is still in sync with your needs and yet allows other
people an easier way to get the mtime from the file data.


In regards to locking, there are two functions in the tools package for
locking and unlocking access to a file.  They're based on portalocker code
from the Python Cookbook site.  They should definitely work on Linux.  If
you try using them and have problems, send an email to the pyblosxom-devel
list.

/will


On Thu, 19 Aug 2004, Wai Yip Tung wrote:
>
> I'm looking at 2. with an index file. I was concerned that pyBlosxom
> would walk through the whole datadir everytime it was invoked. The price
> is even heavier if in addition it has to read inside each entry. The
> index file is to kill two birds with one stone. Perhaps we can add
> another command line option to pyblosxom.cgi to do the indexing so that
> they can make use of the same framework and configurations instead of
> writing a separate script.
>
> Another question perhaps you can help is how do we lock a file from CGI,
> in particularly in Linux? I wonder what would happen if the index update
> and pyBlosxom were invoked at the same time.
>
> Wai Yip


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285