Re: filestat

That's kind of part of option 2.  The solution gets pushed to the plugin
which would pull the mtime for a given file based on the filename from an
index file.

Then either the mtime index file could be built manually, or it could be
built using a cron job (or some similarly automatic process).

/will


On Thu, 19 Aug 2004, Blake Winton wrote:
>
> will guaraldi wrote:
> > 3. Some third option I haven't thought of.  (I'm all ears if other people
> > have other ideas.)
>
> I'm the official Idea Guy, right?
>
> How about having a file in the root consisting of lines of the form:
> <path to the entry> <datetime to use for that entry>
> ?
>
> Then we would only have to open and read one extra file, which shouldn't
> slow things down too much.
>
> Just a thought,
> Blake.
>
>
>
> -------------------------------------------------------
> 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
> _______________________________________________
> pyblosxom-users mailing list
> pyblosxom-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users
>

-- 
whatever it is, you can find it at http://www.bluesock.org/~willg/
except Will--you can only see him in real life.


-------------------------------------------------------
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