Ken Starks wrote:
[...]
I did have a few images that were stored also in a database, but I
would pre-process them in a seperate stage, generating a local copy,
and populating a table of the database with the path. This was a
batch process, not an interactive one, and it used python rather than
cocoon. (Actually, it could do a minor amount of image-processing as
well, such as cropping, changing contrast, creating thumbnails,
changing to a different format, Etc and used Image magick as well as
python).
I do something very similar, taking in Word XML documents. The
preprocessor extracts any encoded image data, converts them back to
image format, creates thumbnails and web-res versions, and adds details
of them to an XML file in their directory, rather than using a database.
The XSL[T] processes then reference them externally as images, which is
probably faster than doing database extraction and image conversion in
real time.
I suppose it depends on the amount of storage you have, and how
important it is to you to store your images on a database.
In this case there are typically only a handful of images, so a database
would be overkill: YMMV.
///Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
