| commit | 699309efe70005f60c83a31cca344eab96e7596e | [log] [tgz] |
|---|---|---|
| author | haoyuewang <haoyuewang@google.com> | Fri Sep 24 12:43:09 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Sep 24 12:44:09 2021 -0700 |
| tree | 121d852bf28c29826349c2c0ecdedd5af1571fe2 | |
| parent | 08ca146e0d39504e8f3e25c415c46b440161d2c1 [diff] |
Separate (1) feeding frame to pending stream & (2) processing pending stream in QuicSession::PendingStreamOnStream to different functions controlled by different knobs (ShouldProcessFrameByPendingStream & ShouldProcessPendingStreamImmediately). In followup, knobs in (1) & (2) can be used to buffer stream data until post-tls handshake completes. PiperOrigin-RevId: 398791682
QUICHE stands for QUIC, Http/2, 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.