| commit | 90315e8698e0d2290a8a0fdfe96318ebb1a210a7 | [log] [tgz] |
|---|---|---|
| author | danzh <danzh@google.com> | Thu Jun 08 14:09:49 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jun 08 14:10:36 2023 -0700 |
| tree | 70a07547ebcc2ebe7533acb11932ed6381e800f3 | |
| parent | 7c0ef5f55e38c17cb5d181f8ca74e2925602c78c [diff] |
When a QUIC client probes from a new socket via a new writer or respond to peer's probing on a new socket, check if the socket is write blocked. Currently QuicConnetion blindly write packets to the new socket, and let the platform to decide how to handle socket blockage case. It is okay if the platform silently drop the probing packet in this case. But Chrome added CHECKs to disallow QUIC to write to socket which is already blocked: https://bugs.chromium.org/p/chromium/issues/detail?id=1376754#c10. So this change is to address the CHECK violation there and unblock their further debugging on the original issue. PiperOrigin-RevId: 538886916
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.