1.) What features not yet implemented should go into the Slide 2.0 release?
If Slide is considered a content repository as a combination of underlying stores, global locks that live for the duration of a transaction might be considered. A generic multilevel lock implementation already exists for the tx store and can easily be reused in a non-blocking mode. A problem may be lock propagation to parent resources if needed. Intention locks might discussed...
As discussed earlier in this mailing list and as Daniel already noticed, this is not needed for correctness, but might reduce the danger of deadlocks to a more reasonable level and enables reporting of conflicts on a pre-store tier.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
