| commit | bdfa955e94c58b60a96a995db7de6f02f4f8a007 | [log] [tgz] |
|---|---|---|
| author | asedeno <asedeno@google.com> | Mon May 08 10:00:13 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon May 08 10:01:16 2023 -0700 |
| tree | cc02d52019b6c50b5435a362e02a99628658ed6c | |
| parent | d907cd88312862f0577833c73c13e1b3bd51b090 [diff] |
masque_utils: open tun_fd with O_NONBLOCK This lets the infinite loops that read() these file descriptors actually break when there's nothing to read, allowing the rest of the masque server and client to run and move packets. PiperOrigin-RevId: 530332710
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.