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

Re: Traffic Flow for Remote Sites

From: Simon Large <simon.tortoisesvn_at_gmail.com>
Date: Wed, 19 Aug 2015 09:19:02 +0100

On 19 August 2015 at 00:33, Kym Charlesworth <kym.charlesworth_at_ifaa.com.au>
wrote:

> I have TortoiseSVN installed on my PC in one geographic location
> (Brisbane) but am working on a repository in another geographic location
> (Melbourne) via a mapped drive.
>
> There is one VisualSVN server located in a 3rd geographic location
> (Sydney).
>
>

This makes no sense. How can the server be in a different geographic
location from the repository? I'm guessing you are using the term
repository to refer to a working copy which is completely unrelated. Or
maybe you really do mean that the repository is on a mapped drive and the
server is in a different location, which would be very both very dangerous
to your data and very slow.

If I commit changes on my PC on the mapped drive to Melbourne, is the
> traffic flow from the commit operation Melbourne > Sydney direct OR
> Melbourne > Brisbane > Sydney ???
>

Regardless of what you mean by 'repository', why do you need to use mapped
drives at all? You should never put a repository on a mapped drive. Sharing
a working copy on a mapped drive can work in some circumstances but is not
generally recommended. Sharing a working copy between two people is
definitely not recommended. There are several articles on this in the FAQ.

What problem are you trying to solve by using mapped drives? Very often
people do this (misguidedly) to avoid setting up a server, but you have
already done that part.

Simon

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3132846

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-08-19 12:15:22 CEST

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.