"Itamar S.-T." wrote:
Pavlos Christoforou wrote:
Because the object database stores revisions of objects, each new inciment of the property will append a new revision on the ned of the database. For a million hit per day website, this means a million new objects will be added to the database. Definately performance prohibitive. ...
A simple solution is to write an external method that sores the counter value in a regular file, lets say in the Zope/var directory.
Maybe there should be some way to disable storing of old versions of an object, where Undo isn't necessary? The Gimp for example has a similar command.
In Zope 2, there will (eventually, not initially, but not to long from now :) be an option for using multiple databases in a Zope site. You'll be able to combine databases designed to support undo (e.g. FileStorage) with databases that don't support undo and handle fast changing data better (e.g. dbmStorage, DCOracleSimpleStorage, etc.). There is a similar issue with versions. Jim -- Jim Fulton mailto:jim@digicool.com Python Powered! Technical Director (888) 344-4332 http://www.python.org Digital Creations http://www.digicool.com http://www.zope.org Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email address may not be added to any commercial mail list with out my permission. Violation of my privacy with advertising or SPAM will result in a suit for a MINIMUM of $500 damages/incident, $1500 for repeats.