Re: How are (atomic) commits implemented?

2005/7/18, Ben Collins-Sussman <sussman@collab.net>:
> [please keep this on the list]

Sorry I always forget to hit the "reply all" button.

> What you're talking about above is a different behavior -- it's the
> "on the fly" out of dateness checking that happens as the transaction
> is being constructed. As soon as a client tries to modify a file
> which is out-of-date with respect to HEAD, the whole transaction is
> aborted. This happens long before the 'final' commit of the
> transaction.

What I mean is what following situation:
A and B have the same file at the same revision checked out. They
modify this file. They start to commit this file at the same time.
Neither file is not out-of-date with respect to the current head in
the repository.

What you said earlier in this thread (as I understood) is that each
commit creates a transaction independent of each other, and only the
final phase at end of the commit is serialized. So the first commited
transaction would make the second one invalid, wouldn't it?

I just wanted to hear that either I am wrong, or that subversion
detects that situation and rejects the second commit.

Norbert

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 18 20:36:41 2005