transports and connections

[John Arbash Meinel]

Robert Collins wrote:
> Martin Andrew and I were talking about how to test the smart server's
> ssh hookup. We felt that it would be made easier if we define
> 
> get_transport() as /not/ connecting to the server, but rather the
> returned transport connecting when the first operation is called on it.
> 
> This follows the idiom of having constructors not do complex or time
> consuming things, and also fits protocols like http much better than
> requiring that the result of get_transport mean the server is actually
> available.
> 
> Thoughts ?
> 
> -Rob

I agree, but I'm not sure how it will affect transports that want to
share a connection. So if I connect to the same ssh machine 2 times,
currently bzr will share the sftp connection.

I realize we want to modify how caching/sharing works anyway. But I
wouldn't want lazy evaluation to start causing double connects.

Otherwise, I think it would be nice if get_transport() would not
actually connect.

John
=:->


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060830/63a936c9/attachment.pgp