On Tue, 13 Apr 2004, Kapil Thangavelu wrote:
since objects modified in a version are in essence locked from participating in other transactions, actions like modifying content in a version in a cmf site amounts to locking the catalog from changes outside of the version, which amounts to shutting down write activities to a cmf site.
This is only true of FileStorage. Some other storage could implement ZODB versions with merging capability rather than locking.
i'm also curious how you dealt with svn transactions as part of the ape integration work to date.
The same way it tries to impose transactions on the filesystem: in the vote phase, Ape looks for possible problems and aborts early if it detects anything that will cause the transaction to fail. Obviously, this provides no guarantee, but covers many cases. Shane