Transport.close()

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David Allouche wrote:
> I think it is essential for long-lived clients to be able to explicitly
> close a connection.

Okay.  But since multiple Transports use the same connection, what
should the effect be on the other Transports that use the same connection?

While we don't do a lot of async, I believe that the file objects
returned by Transport.get can be returned before the download is
complete.  So there is the possibility of invoking Transport.close while
an operation is in progress on the same connection.

And even so, it doesn't seem nice to disconnect other Transports that
may have further use for the connection.

But if it just decrements a reference count, it seems a bit silly,
because Transports are already reference-counted.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFFEwDq0F+nu1YWqI0RApXDAKCCoB6RJ7kQ4PRbkVfolHvPNEo5JwCfRFm6
7ZM+uOfvtIHELIpPn7VrCxc=
=qVrw
-----END PGP SIGNATURE-----