| commit | da41ea34d762b9f3856f34e859c1334f25109e2c | [log] [tgz] |
|---|---|---|
| author | ericorth <ericorth@google.com> | Tue Apr 22 13:41:16 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Apr 22 13:42:10 2025 -0700 |
| tree | 55ec954c89919ef6891e927c420c06da8e125d9c | |
| parent | 1f8ef8ef16ef60f668f30c7595c59e28a1537eaa [diff] |
Cleanup QboneTunnel threading/shutdown * Move EpollServer out of QboneTunnel into the parent QboneTunnelSilo, so the silo can more cleanly and safely manage the shutdown and destroy the tunnel and all its resources in the silo/epoll thread. * Move ownership of the tunnel into the silo, and force all the silo-external interaction (mostly status retrieval) to go through the silo. Gives the silo a bit more control to enforce thread safety on those calls. PiperOrigin-RevId: 750311878
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.