[MERGE] bzr+http:// should always try POSTing to the same location, not lots of child locations.

[Aaron Bentley]

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

John Arbash Meinel wrote:
> I think it makes sense to have requests for:
> 
> .bzr/branch/foo
> 
> go through
> 
> .bzr/smart
> 
> Rather than .bzr/branch/.bzr/smart
> 
> I'm not sure why you disagree with that.

I think dumb transport operations should be consistent.

We've defined that get_transport('x').clone('y') is equivalent to
get_transport('x/y').  This breaks that.  It penalizes behaviour that we
should be rewarding, because if we can use an existing transport to
acquire another BzrDir, that is a performance win.

This is addressing the issue at the wrong layer.  Instead of changing
the way dumb transports work, implement a SmartBzrDir.  We want to do
that anyway, don't we?

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

iD8DBQFFo7n80F+nu1YWqI0RAqL2AJ0VxZi2OtCq0BNbFRQoOgqHCPDrZgCbBdoa
K56f6du5bqoGyBOMchdkSdY=
=+gc7
-----END PGP SIGNATURE-----