On Tue, 24 Mar 2009, Adam Heath wrote:
Nicolas Pitre wrote:
Strange. You could instruct ssh to keep the connection up with the
ServerAliveInterval option (see the ssh_config man page).
Sure, could do that. Already have a separate ssh config entry for
this host. But why should a connection be kept open for that long?
Why not close and re-open?
what if the server you are connecting to is behind a load balancer? how do
you know that your new connection will go to the same server? if the
client never reconnects, how long should the server keep it's resources
tied up 'just in case'. if something connects to the server, how does it
know if it's something reconnecting or connecting for the first time? (or
someone connecting with the intent of messing up someone else's fetch)
having the client reconnect to finish a single transaction starts getting
_really_ ugly.
David Lang
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
