| commit | 419df03d82a1eafbb48725ac98a552fc89962591 | [log] [tgz] |
|---|---|---|
| author | rch <rch@google.com> | Tue Jun 10 14:58:52 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jun 10 14:59:48 2025 -0700 |
| tree | 0b6fb434a318250dcc72a3c24d83e330420f2eeb | |
| parent | 1f00f1a662b7854a1db9592241da3bf3e7dd8052 [diff] |
Change the Hyperloop client initial stream flow control window to 16KB, but then raise it to 4MB in the stream itself. This is in preparation for fixing the dynamic flow control window logic in a follow up. Breaks out some of the code protected by gfe2_restart_flag_track_hyperloop_streams4 into a new flag. gfe2_restart_flag_track_hyperloop_streams4 will remain disabled until this new flag is removed. Protected by gfe2_restart_flag_move_hyperloop_stream_flow_control. PiperOrigin-RevId: 769812846
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.