| commit | 91da99072d60c06dcc5450a0932de4e8834c4a4e | [log] [tgz] |
|---|---|---|
| author | bnc <bnc@google.com> | Tue Mar 15 18:14:48 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Mar 15 18:15:34 2022 -0700 |
| tree | 891d602d38115b054f0f9368e93bbaef1254c2b0 | |
| parent | 98f41e62dcdf062a9fa7596dcb75135b23f9eb3b [diff] |
Move quic_client_stats to quiche/common/platform/default. Also break up quic_exported_stats for clarity, and leave a quic_client_stats API behind that points to quiche/common/platform/api/quiche_client_stats (because there are too many callers to migrate them all in this CL, besides server stats should probably be moved and migrated at the same time). PiperOrigin-RevId: 434909766
QUICHE stands for QUIC, Http/2, 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.