g
Sent: Tuesday, January 10, 2023 11:23 PM
To: Dmitry Karpov via curl-library
Cc: Dmitry Karpov
Subject: [EXTERNAL] Re: H3/QUIC flow control/buffering problem and suggestion
On Tue, 10 Jan 2023, Dmitry Karpov via curl-library wrote:
> It would be great if all QUIC backends implem
On Tue, 10 Jan 2023, Dmitry Karpov via curl-library wrote:
It would be great if all QUIC backends implemented such functionality and
provided API to tune it. Otherwise, we would need to implement such
"background buffering" in libcurl code wrapping that backend to match TCP
"background"
ibcurl
is very important to make H3/QUIC truly competitive with H1/H2.
And as H3 in libcurl is moving toward production-ready state, it is something
to think about.
Thanks,
Dmitry Karpov
-Original Message-
From: Daniel Stenberg
Sent: Tuesday, January 10, 2023 12:02 AM
To: Dmitry Kar
ance.
Thanks,
Dmitry Karpov
-Original Message-
From: Daniel Stenberg
Sent: Monday, January 9, 2023 1:57 PM
To: Dmitry Karpov via curl-library
Cc: Dmitry Karpov
Subject: [EXTERNAL] Re: H3/QUIC flow control/buffering problem and suggestion
On Mon, 9 Jan 2023, Dmitry Karpov via curl-library
On Mon, 9 Jan 2023, Dmitry Karpov via curl-library wrote:
In H3, Curl's internal buffering also controls QUIC internal buffering,
While this might be the case right now for one/some/all of the backends, I
don't think this is something that is carved in stone. curl uses the buffer in
one
l Message-
From: curl-library On Behalf Of Daniel
Stenberg via curl-library
Sent: Saturday, January 7, 2023 7:07 AM
To: Daniel Stenberg via curl-library
Cc: Daniel Stenberg
Subject: [EXTERNAL] Re: H3/QUIC flow control/buffering problem and suggestion
On Sat, 7 Jan 2023, Daniel Stenberg via curl
On Fri, 6 Jan 2023, Dmitry Karpov via curl-library wrote:
So, I suggest to provide a new "QUIC" option (similar to the "TCP" options
that we already have): CURLOPT_QUIC_BUFFERSIZE which will do similar steps
that I did but in just one option setting call and without the need to
modify libcurl
Hi All,
As H3 in libcurl is going steadily to the production feature, I would like to
tell about one H3/QUIC issue, which was OK for the experimental stage, but
probably needs to be addressed to make H3 a full production feature.
When I was comparing H3/QUIC with the H1/H2 TCP in my local
