| commit | 15c43d01932853c18455499e4795647a28c96b36 | [log] [tgz] |
|---|---|---|
| author | martinduke <martinduke@google.com> | Thu Sep 26 14:00:37 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Sep 26 14:01:40 2024 -0700 |
| tree | 7976692a0a980db5ce4b2ac7e6609e0bec078dcd | |
| parent | 9316bd7408f82be526895fcdb3d28ccceb9df5b8 [diff] |
Complete processing of RESET_STREAM_AT frames. Negotiate with transport parameters and pass the frame from QuicConnection to QuicStream. This could be an MVP; it is compliant to negotiate, process, and never send. But a sending CL will follow. PiperOrigin-RevId: 679284591
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.