Re: server transactions

All this sounds fine. The transactions will be first-class objects in
the database, and the transaction id will simply be the key for a
given transaction.

Will transactions be live while the DAV module talks to the network?
If so, then I think it follows from the "your flaky network connection
doesn't impede my access" rule that we don't report conflicts between
two transactions until one of them has actually committed ---
otherwise, some transaction A in progress could lock up some
resources, but then its network connection might go south.

On the update side, the FS interface should let you do things pretty
much however you want.
Received on Sat Oct 21 14:36:07 2006