[Zope] Storing published objects (?)

[Samir Mishra]

Jamie,

Thanks for the response. I think you misunderstood my question. I'm not
looking to implement a cache manager.

What I'm looking to do is, not store the page for a few minutes/hours, but
months. Or longer. I also want external apps to have access to the rendered
page. 

I have to generate weekly financial reports. The data for each report is
from NUMEROUS sources. So the query, formatting etc. are complex and time
consuming. The weekly report gets updated over the duration of the month,
but at the end of the month the report is frozen. So once the report is
published, it will almost NEVER be changed. We may publish corrections to
the report, but these will be labelled as corrections, and will not replace
the originally published document. 

I'd rather not have to re-create the report every time it's viewed. I'd
prefer to save the HTML representation of the report as a BLOB in a database
(and later extend this to PDFs of the same). And that's what I'm hoping to
do - assign the results of a page rendered by Zope, i.e., all of the HTML
generated, to a binary column in a DB.

OT: I believe Berkeley DB is extremely fast for this sort of
indexing/retrieval. Anyone have any experience?

Hope that's clearer.

Thanks again.

Samir.

-----Original Message-----
From: Jamie Heilman [mailto:jamie@audible.transient.net]
Sent: Wednesday, May 28, 2003 08:25
To: Samir Mishra
Cc: zope@zope.org
Subject: Re: [Zope] Storing published objects (?)


Samir Mishra wrote:
> The underlying SQL queries are complex, the data doesn't change often, and
I
> think this may be the best way to lighten the burden on the DB.

Hmmm, well generally this is what CacheManagers do, but storing the
results in a database would be a new one (to date I've seen managers
that use memory, the filesystem, and just add HTTP headers to the
response).  While its entirely likely you could achieve what you want
using a memory cache, if the data is sufficiently large it may be not
be a good idea, and its certainly not persistent accross
zope-restarts.  Implementing a cache manager that stored its data in a
RDBMS shouldn't be impossible, take a look at the Cache & CacheManager
interfaces in OFS/Cache.py -- and I'd suggest using the updated code
I've prepared in http://collector.zope.org/Zope/911 as its cleaner
than the existing stuff.

-- 
Jamie Heilman                   http://audible.transient.net/~jamie/
"It's almost impossible to overestimate the unimportance of most things."
							-John Logue

_______________________________________________
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )