[PERFORMANCE] url encoding

[Robert Collins]

I have a thought about a good compromise for performance in our
transport layer.

Each Transport is a handle to a directory... and URLs from users are
broken into two parts:

- the directory we connect to
- the file the user specified

After that split, all the file operations we perform, including
subdirs-from-the-user-dir, are generated by bzr, and are strictly ascii.

It seems reasonable to me that we could encode this in the api of
Transport - that is, 'transport.put(foo)' would expect an ascii only,
non unicode, non escaped, relative reference in foo, with no '..'. This
would allow LocalTransport to fast-path all local operations with no
escaping, without running into a mess with predicting encoding on remote
servers.

Aaron and I chatted about this and thought it was reasonable. What does
the larger community think?

Rob
-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060609/32ef27ba/attachment.pgp