| commit | 25487132255dd03ed030d9d3c519b46613705f9f | [log] [tgz] |
|---|---|---|
| author | ericorth <ericorth@google.com> | Thu Sep 22 13:41:57 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Sep 22 13:43:22 2022 -0700 |
| tree | 360dd802ac4305230231e90a1855b26680ab6934 | |
| parent | 80b57843b02d75453017f89fb490998ae1824c7f [diff] |
Generalize EventLoopTcpClientSocket between TCP and connected-UDP Gives us the socket support needed for CONNECT-UDP. As far as interface and implementation goes, connected UDP sockets are pretty much the same as TCP sockets other than one small parameter sent to ::socket(). But the expected behavior is obviously very different, so this CL is primarily added testing for UDP socket expectations. PiperOrigin-RevId: 476185935
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.