Auke Jilderda <auke.jilderda@philips.com> writes:
> Trying to use Subversion at a fairly large project, we repeatedly run into
> some networking issues, causing SVN to bail out with error messages such
> as: "Could not read response body: An existing connection was forcibly
> closed by the remote host." and "Could not create SSL connection through
> proxy server". We suspect it might be our corporate proxy server
> infrastructure that might be causing this but we have yet to track down
> the precise cause.
>
> In any case, it raises an interesting issue: Apparently, Subversion does
> not try to re-connect a busted network connection and I'm wondering why
> that is? Being a networked application that often needs an open
> connection for a prolonged amount of time (e.g. we've seen commits that
> take over two hours), it might be wise to provide some sort of graceful
> degradation (e.g. trying once or twice to restore a broken connection
> before bailing out). Any arguments in favour or against this?
I feel a little uncomfortable making Subversion take on
responsibilities that should belong to the transport layer. Wasn't
TCP supposed to take care of this stuff for us? If it's not, can we
realistically do much better?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 29 17:04:34 2004