On Wed, Jun 16, 2010 at 2:41 PM, Will Shackleford <shackle_at_cme.nist.gov> wrote:
>
>
> We have a lot of trouble with the fact that subversion needs to use multiple
> ssh connections to do a
> single svn update. Our firewall only allows one connection through before
> you have to login to the firewall
> again. (which is an incredible pain)
> Also tortoisesvn doesn't seem to be integrated with an ssh-agent so the
> windows users need to
> type their username and password 3 times even when not going through the
> firewall.
>
> Directly accessing the repository files or using the pserver are not really
> options for us, given the
> need to administer users and open up the network ports etc.
>
> Is there a way it can be reconfigured now to use only a single ssh
> connection now or
> should submit and issue for this to be fixed later?
The Subversion client has a bad habit of treating repository access
connections (whether they be http, svn, or something else) as cheap
resources. Of course this is an invalid assumption, but it hasn't yet
been addressed by the developers. A couple of us talked last week
over dinner about the potential of being more intelligent about
reusing connections, but there isn't any definite timetable to do so.
So yes, Subversion could be better, but there are other things of
higher priority to the devs right now.
-Hyrum
Received on 2010-06-16 23:22:47 CEST