[MERGE] HTTP smart server

[Vincent Ladeuil]

>>>>> "Andrew" == Andrew Bennetts <andrew at canonical.com> writes:

<snip/>

    >> 
    >> I would rather see us reuse the POST object until we find
    >> that it isn't possible.

    Andrew> It is reusing the POST object, exactly the same was
    Andrew> way as the _base_curl and _range_curl objects are
    Andrew> reused.  Did you mean something else?

I think he meant reuse the _base_curl object :-)

The point is that the connection sharing via pycurl occurs via
the curl objects, so if we use 2 curl objects, we basically have
two connections for each host (each shared by the requests using
the curl object). By introducing a third object we now have 3
connections for each host, not really what we want to achieve :-)

As John explained, introducing the _range_curl object was a
workaround because an option (RANGE) set in the _base_curl object
was not cancelable (sp?, resetable ?) and was in the way for the
next non-range request.

So either you can set your options for your request and reset
them once the request have been answered or you *have* to use a
third curl object.

Hope that clarifies things,

        Vincent