Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: H3/QUIC flow control/buffering problem and suggestion
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-library <curl-library_at_lists.haxx.se>
Date: Sat, 7 Jan 2023 14:12:43 +0100 (CET)
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 for each desired buffer size.
Why does it have to be a new option? Why not just make the existing one
possible to set larger than today?
If an application is willing to use N megabytes for a transfer buffer when
doing h3, surely they can then also be allowed to set the same size for non-h3
transfers?
Date: Sat, 7 Jan 2023 14:12:43 +0100 (CET)
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 for each desired buffer size.
Why does it have to be a new option? Why not just make the existing one
possible to set larger than today?
If an application is willing to use N megabytes for a transfer buffer when
doing h3, surely they can then also be allowed to set the same size for non-h3
transfers?
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://curl.se/support.html -- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2023-01-07