Strict long transactions?

Consider a repository head revision

        dir/foo.c
        dir/bar.c

and two users Alice and Bob. Alice changes foo.c and commits, creating a new
version of the repository. At the same time Bob changes bar.c and tries to
commit just after Alice.

In CVS using local filesystem repository, Bob's commit is rejected, thanks to
the strict long transaction model. However, when using the network
implementation of CVS, Bob's commit is accepted, without an update. The CVS
developers seem to have chosen this solution by design --- a choice that I
think is wrong.

Subversion seems always to accept Bob's commit without a prior update, and I
therefore have a few questions:

1. Am I wrong?
If no,
2. Is this behavior a bug, or is it intentional?
If intentional
3. Why?

-- 
Ch
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org