Re: thoughts on meta-data (was: importing entries)

> Well, then.  I guess to fix these issues, we'd need to adjust the 
> FileEntry as you mentioned so that it opens the file, pulls in the 
> contents of the the file, extrapolates the title, extrapolates the 
> metadata and leaves parsing the body until it's needed.

Sorry Will, have to jump in here. I don't think this idea will scale as 
you have to open every file in the directory to grab metadata, slowing 
things down. And let's say you'd just leave the files open until 
another plugin reads the data, you'll lose file handles faster than you 
can blink.

And talk about actual entries itself, what if the entry is a pure PDF 
(in itself full of metadata, in a different form), or a JPG (EXIF 
data), or even one could have an MP3 parser that reads out the ID3 Tags 
to get text/images (Podcasting anyone? :) can be slow to read ID3v2 for 
example) to display entries, and have the actual file as downloadable 
enclosures.

I would agree to have a metadata scanning function, probably the first 
time it reads a file, and store it in a DB somewhere, and the next time 
pyblosxom runs, only one file gets opened (much like how the cache is 
done right now).

I remember one time a while back, there was a problem with one of our 
plugins which reads data in the files. That slowed down the main (old) 
pyblosxom blog by a factor of 4.



-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click