[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Suggestion for enhancement: separate update and commit urls

From: Ulrich Eckhardt <ulrich.eckhardt_at_dominolaser.com>
Date: Wed, 12 Jan 2011 08:38:47 +0100

On Wednesday 12 January 2011, Jeff Hoag wrote:
> I have a suggestion that would make Tortoise easier to use in a
> wide-geography usage model. We have a subversion server set up in Israel,
> and have a number of (one-way) mirrored sites around the world, including a
> mirror in Oregon where I am. It is much faster for me to check out and
> update code, view the log and other read-only type activities if I
> reference the server at my local site; but commits must be done directly to
> the the main server in Israel. I can switch between the two archives
> manually, but this is rather tedious.

You can set up a transparent write proxy with Apache. This is even described
in the manual, somewhere near the svnsync docs.

> It would be great to have a option where Tortoise could have separate
> update-from and commit-to urls. If this option were selected, updates
> would automatically come from the (near-and-fast) update-from server, as
> well as blame searches, diffs and all the read-only activities.

Nah, nothing that TSVN could do would actually guarantee that things are
consistent. The server-side write proxy is the better choice.

> Since there is somewhat of a time delay between mirror operations, even
> if I did an update from the mirror, there could be very fresh changes
> on the master site that had not yet been mirrored, so the commit
> function would probably have to do several things: switch to the
> commit-to server, check to see if an update is required, notify user &
> ask whether update only/update & commit/cancel, then update from
> commit-to server, commit, and switch back to the update-from server
> as requested.

There's no reason to check for updates with this any more than otherwise.
There is always the possibility that someone committed a revision between you
last updating your WC and starting to commit one yourself. If you start a
transaction, the server checks if the base of the new revision is
sufficiently new.

That said, you can use a local TCP proxy that you redirect to either of the
repositories, depending on what you are doing. TSVN would be completely
ignorant thereof, other SVN clients would also just work without knowing it.



ML: http://tortoisesvn.tigris.org/list_etiquette.html
FAQ: http://tortoisesvn.net/faq
Domino Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
Visit our website at <http://www.dominolaser.com/>
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Domino Laser GmbH ist für diese Folgen nicht verantwortlich.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-01-12 08:37:55 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.