commit | eea13878ce336a9e56dbb58437abc148df5c3d5f | [log] [tgz] |
---|---|---|
author | QUICHE team <quiche-dev@google.com> | Wed Feb 09 13:33:25 2022 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Feb 09 13:34:31 2022 -0800 |
tree | d904c5fde2ff26b7f84e3b745f2c630b3f41618d | |
parent | b5824c589ce35636fbeb5483f6b3faf2e8463453 [diff] |
Interprets SETTINGS_INITIAL_WINDOW_SIZE from the peer. Once the setting is received, the session will use the new value for all streams created subsequently. In addition, the send window for any existing streams is updated by the delta between the old and new values. PiperOrigin-RevId: 427558116
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.