On 5 Dec 2003, at 02:17, Andreas Hartmann wrote:
Stefano Mazzocchi wrote:
I looked into the repository block and I find a *lot* of things (locking, permissions, properties) that look very much like a duplication of effort. The Slide project spent years optimizing and polishing issues like transactionality and locking, do you really want to implement a layer to "emulate" those things in case the given source is not capable of handling it itself?
I have a basic question: When you talk about a "repository", does this imply that operations on ressources are transactional, or is this an optional feature?
That's up to us to define what level of transactionality we want/need/able-to-implement-shortly.
For me, now, transactionality is not that important, but it would be a good thing to have (for example, making the saving of one document that contains images an atomic thing)
-- Stefano.
smime.p7s
Description: S/MIME cryptographic signature
