Comment 6 for bug 803187
Revision history for this message
| Andrew Bennetts (spiv) wrote Re: [Bug 803187] Re: SSH connections should be explicitly closed, not rely on gc | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Vincent Ladeuil wrote:
> > It requires the API user to care about the connection timeout.
>
> Right, but the same kind of constraint already applies to http
> transports for example and the strategy there has been to reconnect
> transparently on transient errors. I suspect the same kind of approach
> could be taken for ssh transports.
Perhaps. It will be less than transparent for some users: they will get
prompted for a passphrase. And it's much more expensive in roundtrips
to reestablish an SSH session than it is to make a new HTTP connection.
Reconnecting is probably a tolerable compromise, but it's not ideal.
Ideally we'd avoid disconnecting connections unless we are certain they
aren't wanted, or are wasting resources (e.g. we are running low on
fds).
-Andrew.