quic

Describe the feature you'd like supported

We should change the CID after enough idle time so that any possible NAT rebinding would be harder to be tracked by an outside observer. The simplest way to implement this would be in the flush send code path. When first starting a flush, check how much time has elapsed since the last send. If it's greater than X (20? 30?) seconds force a CID update

I believe these are the knobs for data limits:

https://docs.rs/quinn/latest/quinn/struct.TransportConfig.html#method.stream_receive_window
https://docs.rs/quinn/latest/quinn/struct.TransportConfig.html#method.receive_window

Would like to be able to set these per-connection.

Also, would be great to release this: quinn-rs/quinn#1315

I suppose if a client violates

Motivation

I recently ran into an issue where an exception thrown in Micrometer caused my request to break. The actual issue I ran into is not in reactor although reactor was used. However as reactor uses Micrometer as well and e.g. [here|https://github.com/reactor/reactor-netty/blob/main/reactor-netty-core/src/main/java/reactor/netty/channel/AbstractChannelMetricsHandler.java] there also does

file echo_client.c, line:121 st_h->read_stdin_ev = event_new(prog_eb(st_h->client_ctx->prog),
STDIN_FILENO, EV_READ, read_stdin, st_h);

A place to track new events or additional data to existing events. The original event work can found at: aws/s2n-quic#439

• platform fatal IO error (Not sure how we're going to get this one done. If you look at the code where the event should be emitted, the endpoint is consumed just before we emit the event, in the event_loop function, meaning that we no longe

https://curl.se/libcurl/c/CURLOPT_PREREQFUNCTION.html

Added with libcurl 7.80