| commit | 60abf6c9d0f0d54b98a4eabe86cc3a8c3f2e6430 | [log] [tgz] |
|---|---|---|
| author | ericorth <ericorth@google.com> | Thu Aug 11 09:36:27 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Aug 11 09:37:57 2022 -0700 |
| tree | 081ae8f078034df2b0e8caf5cea9a4188969d417 | |
| parent | c2de160fd2fb3b2f447e7e644e87cbd0644bbf4b [diff] |
Fix a memory destruction ordering issue in RushIngestQuicServer quic::QuicServer relies on an unowned pointer to a quic::QuicSimpleServerBackend. video_live::RushIngestQuicServer extends both, passing itself to the quic::QuicServer constructor. To be done safely, video_live::RushIngestQuicServer must set the correct base class order to ensure constructors and destructors are called in the correct order. PiperOrigin-RevId: 466976602
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.