On Sun, 3 May 2015, Alcides Viamontes Esquivel wrote:
Thanks for the tip, the pipelining message is no longer in curl sources: an
older version was being used at runtime in the test program, my blunder!
I can confirm that it works concurrently!
Cool, yes I needed to make some adjustments to
>
>
>>
> It could be worth figuring out why curl says so, but it certainly explains
> why it waits with the second request... as we're re-using the pipeline
> concept internally even for multiplexing.
>
>
Thanks for the tip, the pipelining message is no longer in curl sources: an
older version was
On Sun, 3 May 2015, Alcides Viamontes Esquivel wrote:
This is cool. I was playing with your code and noticed that so far it does
one request after another... or so it seems to me. Just in case you have any
use for it, I'm putting below curl's log.
It doesn't for me. I've done three parallel t
>> Hm, btw, I think I'll also push my http2 test setup to github in case
>> someone wants to play along. I'll do that in a separate test repo and
I'll
>> mention it here when it is up.
> My playground area for testing my multiplexing work is now on github:
> https://github.com/bagder/curl-http2
On Tue, Apr 28, 2015 at 09:17:54AM +0200, Daniel Stenberg wrote:
> There are some outstanding questions, like if we should do this by
> default without any options to ask for it and if we really should
> forcibly limit the number of connections to the same host to one.
> And I'm sure there will pop
On Thu, 30 Apr 2015, Yehezkel Horowitz wrote:
I've started out this week working on HTTP/2 multiplexing for libcurl. My
idea is that when using the multi interface and adding easy handles, all
handles that identify the same "origin" (host + port + protocol combination
really) will use the same
Hi Daniel
> I've started out this week working on HTTP/2 multiplexing for libcurl. My
> idea is that when using the multi interface and adding easy handles, all
> handles that identify the same "origin" (host + port + protocol combination
> really) will use the same single connection and do "re
On Tue, 28 Apr 2015, Daniel Stenberg wrote:
Hm, btw, I think I'll also push my http2 test setup to github in case
someone wants to play along. I'll do that in a separate test repo and I'll
mention it here when it is up.
My playground area for testing my multiplexing work is now on github:
On Tue, 28 Apr 2015, Lucas Pardue wrote:
The connection management issues are interesting, after rereading section
9.1 of the HTTP/2 spec it seems like having to set a value for either
CURLMOPT_MAX_HOST_CONNECTIONS or CURLMOPT_MAX_HOST_HTTP2_CONNECTIONS would
be a bit awkward. The spec states
Hello Daniel,
It is good to see work starting on this feature.
> Right now I need CURLMOPT_MAX_HOST_CONNECTIONS set to 1 to really
> stay on one connection only, and again, this may be fine for HTTP/2-only
> users but it may not be what users want for all protocols at once. Not sure
> how to hand
10 matches
Mail list logo
