[rfc] [patch] pycurl transport

[Martin Pool]

On 10 Jan 2006, John A Meinel <john at arbash-meinel.com> wrote:

> What about gzip encoding. Weaves compress quite well. And it could cause
> as much as a 4x download speed increase.

So do you mean doing gzip transfer-encoding, to take advantage of
something like mod_gzip on the other end?  That should be good.  

Though I think in general we'd want to actually create the weaves as .gz
files so that it works regardless of the server.  I'd like to put in
such a feature if you could find your branch that did it.

> But I agree with Jamie. If you get as much of an increase as you say,
> it is worth using if available.  Kind of like cElementTree, only not
> as necessary.
> 
> Oh, and it would be nice if you could actually use a HEAD request for
> 'has', and do a partial download for a get_partial request.

Good point.

> Though I'm not sure how it compares with the knit changes to
> transport.  Since they were switching to returning file-like objects
> that support seek(). (Which I think makes it difficult to do a partial
> read, unless all file-like objects return by Transport would also
> support scatter read).

Perhaps you could defer doing the request until they seek & try to read,
then read from that point on.

-- 
Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060112/c7f1ca9b/attachment.pgp