Jim Fulton wrote:
Alexander Staubo wrote:
Good point; it's the exact same reason why the second version of my Guest Counter product is broken. (Nasty -- I quality-assured the wrong script before sending it off to production ;-).)
Is there any way to create objects that are persistent during the lifetime of the Zope process?
There is a way from C for objects that don't change. Maybe there should be a hook to allow this from Python. Or a hook saying that you don't want an object to be deactivated. Would you want the hook to apply to individual instances, or to classes?
<blue_sky> Hmm, perhaps persistence/caching options should be settable at all points within the object hierarchy, and acquirable. This means that persistence/caching options should be settable on a ZClass, but overridable on a particular instance. </blue_sky> Michael Bernstein.