...This however raises a new issue: the whole operation should be atomic and (somehow) transaction-aware. If for any reason the Dasl component cannot update the database, an error should be thrown and the operation should fail. Interesting problem, and I don't actually see a way to solve it OOTB....
Right, I don't think it is possible to run a transaction between the webdav backend an an internal properties store.
The best we could do is to detect the problem (couldn't update local store) and report it, but it might be hard to recover.
-Bertrand
