cURL / Mailing Lists / curl-library / Single Mail


Re: libcurl and http2

From: venkatesh perumalla <>
Date: Thu, 5 Sep 2013 23:18:12 +0530

Little explanation in below link.

In case of pipeline mode, it is gaurantees that we get in the same sequence.
Suppose if multi handle has E1, E2 & E3 which has same physical
In multi, it takes one after the other easy handle, So when data arrives at
that socket, we directly update E1 status and data.
Also in *curl_multi_runsingle,* we directly update the E1 status.

In case of http2 or spdy, if we use same multi interface, if we read from
socket, it would have come for E2 or E3.
May be we can apply some logic, getting the all the easy handles form multi
and update the corresponding Easy handles.
But in *curl_multi_runsingle,* we directly update the E1 status.

On Thu, Sep 5, 2013 at 9:43 PM, Daniel Stenberg <> wrote:

> On Thu, 5 Sep 2013, venkatesh perumalla wrote:
> for supporting the http2, will you be providing the new inteface? other
>> than easy and multi interface.
> No. I don't see any need to. Do you?
> As per protocol of spdy and http2. Responses are not sequential, response
>> order can be anything. Also has priorites.
> Like with 1.1 each request gets a response. Sure, it can do multiple
> streams over the same physical connection but they are still requests that
> get responses. And priorities can easily just be a new easy_setopt option
> if we think we need that feature.
> Whether you have plan to integrate with multi interface?
> I think it can be made to work just like pipelining with libcurl does
> today.
> But sure, if you have ideas or bring patches I'll listen to other
> suggestions. We're still very early in the http2 area.
> --
> /
> ------------------------------**------------------------------**-------
> List admin:**listinfo/curl-library<>
> Etiquette:**etiquette.html<>

List admin:
Received on 2013-09-05