[Zope] Caching on-the-fly resized photos (implemented)
Ron Bickers
rbickers-dated-1005231330.86f798@logicetc.com
Thu, 1 Nov 2001 09:55:31 -0500
> -----Original Message-----
> From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of
> Markus Schaber
> Since ZODB doesn't keep an access time,
> I could just
> > use the mod time and update it when the display is requested.
> The problem
> > with this is that it would cause a large number of writes to
> the ZODB, and
> > since ZODB is append only, it would quickly bloat.
>
> Why don't you invent an "access time" attribute yourself, and
> just update it at every access?
Updating any attribute (including my own access time attribute) on every
access would cause Data.fs to bloat quickly, because updating an object
appends a new version of it to the end of the file. This means that on
every view of an image, Data.fs would grow by at least the size of that
image.
Also, the advantage of using the built in mod time is that the age is
automatically reset any time the object is modified, so I don't have to keep
up with it every place it might be updated.
_______________________
Ron Bickers
Logic Etc, Inc.