Redo the logic for buffering incoming streams until SETTINGS arrive. Currently, we stop buffering whenever we receive any setting value, but we notify the streams to be unblocked only whenever we finish processing the SETTINGS frame on the control stream. This is inconsistent, and also has a bug where an empty SETTINGS frame does not unblock the connection. This CL makes both occur at the same time, once, at the moment when the SETTINGS frame arrives on the control stream. PiperOrigin-RevId: 542196032
QUICHE stands for QUIC, Http, Etc. It is Google‘s production-ready implementation of QUIC, HTTP/2, HTTP/3, and related protocols and tools. It powers Google’s servers, Chromium, Envoy, and other projects. It is actively developed and maintained.
There are two public QUICHE repositories. Either one may be used by embedders, as they are automatically kept in sync:
To embed QUICHE in your project, platform APIs need to be implemented and build files need to be created. Note that it is on the QUICHE team's roadmap to include default implementation for all platform APIs and to open-source build files. In the meanwhile, take a look at open source embedders like Chromium and Envoy to get started:
To contribute to QUICHE, follow instructions at CONTRIBUTING.md.
QUICHE is only supported on little-endian platforms.