At 1:09 PM -0500 9/23/03, Ben Collins-Sussman wrote:
>"Kenneth Olving" <Kenneth.Olving@frameworx.com> writes:
>
> > A follow up: in the case of svn:externals which brings in >1
>> physical repo (or a manually nested repo as described above), will a
>> commit be atomic across repos?
>
>Nope. That's a Really Really Hard Problem. Instead, you should get
>exactly one atomic commit per unique repository.
>
> > I doubt it at this stage since I haven't seen any mention of TPC and
>> distributed txns but...technically Berkeley DB seems to support
>> XA. Is there any plans at all to provide XA capability in svn?
>> Something like that would be absolutely fantastic, not only in the
>> >1 repo case, but also to coordinate between, say, a repo commit and
>> entries made into some XA aware db.
>
>Yes, it would be nice, but no concrete plans yet. We're about 10
>years behind Clearcase right now. :-)
Well, in this area, Subversion is some unknown number of years
*ahead* of ClearCase, since CC does not offer transactions at all,
nor have I heard any promises to do so. Likewise, CC does not allow
anything like svn:externals (nested repositories/workspaces), unless
you're willing to count "versioned symlinks."
But in places where it's ahead (particularly release management,
branches, and merging), ClearCase has more like a 20 year head
start. 10 years is only when the name was changed from Domain
Software Engineering Environment (DSEE) to ClearCase (with a brief
whistle-stop at "Millenium").
--
-==-
Jack Repenning
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
o: 650.228.2562
c: 408.835-8090
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 23 20:21:46 2003