> Sure, but we also have to accept that you might try a h3 request to an old
> server on the other side of the globe via a slow network.
> A 50-100 ms delay maybe?
I would use 50ms as the default (the lowest in your range 😊).
If h3 server is slow to respond then we may waste one or a few connect
On Thu, 12 Jan 2023, Dmitry Karpov via curl-library wrote:
Daniel, a question about the "Happy eyeballs everything!" section in the
blog. Is the "happy eyeballs" interval between H3 and H2 going to be
controlled by the same option as the interval between IPv6 and IPv4 or there
will be a specia
Daniel, a question about the "Happy eyeballs everything!" section in the blog.
Is the "happy eyeballs" interval between H3 and H2 going to be controlled by
the same option as the interval between IPv6 and IPv4 or there will be a
special option for that?
I am asking because QUIC in H3 is supposed
On Wed, 11 Jan 2023, Dan Fandrich via curl-library wrote:
Writing the same thing as the first line of -v output would double the
chance it's actually seen.
The PR has been updated to this effect now.
--
/ daniel.haxx.se
| Commercial curl support up to 24x7 is available!
| Private help, bu
On Wed, 11 Jan 2023, Kamil Dudka wrote:
Unless someone uses `curl -V 2>&1 | grep ...` like curl's autoconf test did it
with GCC:
https://github.com/curl/curl/commit/curl-7_49_1-45-gb2dcf0347
If they do then they, like us, will learn that it is wrong! =)
--
/ daniel.haxx.se
| Commercial
On Wed, 4 Jan 2023, Daniel Stenberg via curl-library wrote:
I wrote a blog on this topic:
https://daniel.haxx.se/blog/2023/01/12/selecting-http-version-three/
I also created a plan for what's next by updating the gist I already
mentioned: https://gist.github.com/bagder/6475a32d7cdc0b54f2dd654
