It sounds like the problem that would come from storing session data in ZODB. One nice solution (as someone pointed out for me) would be to have multiple parallell ZODB-storages. One for the normal transactional ZODB(filebased or RDMS-based) and one non-transactional for session-data and cache-data. Both would be distributed by the ZEO for failover and scalability. Regards, Johan Carlsson
The ZCache Product I created has one major problem - every time it updates itself it'll make the ZODB grow, since it stores all the old contents it had. I don't want this to happen - there's no reason why anyone should undo a change to the cache. I do however want the contents of the ZCache to be stored on disk when it gets moved out of the Zope cache, so I don't want to use volatile variables.
Is there any way to do this? Or is it impossible?
-- Itamar S.T. itamars@ibm.net
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev No cross posts or HTML encoding! (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )