| commit | 89d3b8ac58c523fba41356ea560cf95c9c451790 | [log] [tgz] |
|---|---|---|
| author | ericorth <ericorth@google.com> | Tue Aug 09 08:29:21 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Aug 09 08:30:47 2022 -0700 |
| tree | 1ccd9dc9c69741216726354a2a8764966da02792 | |
| parent | b95fbe74be46e3d888824ad6c1f1d42f0f00aa5b [diff] |
Add higher-level TCP client socket/factory support to QUICHE Added some basic interfaces that could be used to abstract away implementation details of socket operations, including a SocketFactory that allows initiation details like QuicEventLoop to be hidden away from code interacting with it and creating/running sockets. Especially helpful to pass factory objects to code that doesn't need to know details around the event/async libraries in use or need to stay agnostic between them to build on multiple plaforms/environments. Interfaces support my current needs (TCP client sockets), but left them deliberately open to future expansion to server sockets or UDP, etc. Created a QuicEventLoop-based implementation of the interfaces. PiperOrigin-RevId: 466366913
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.