| commit | 98c9cdb4cd17ea043243037bfdee3cdf024cab54 | [log] [tgz] |
|---|---|---|
| author | davidben <davidben@google.com> | Wed Apr 09 13:56:12 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Apr 09 13:57:15 2025 -0700 |
| tree | ea372aa45232465c523bc15545caeb93d8167075 | |
| parent | 67cf174c11c1fef1d4571a4cfa576739677c2947 [diff] |
Remove now unnecessary calls to CRYPTO_library_init This was already almost always a no-op, except when built with BORINGSSL_NO_STATIC_INITIALIZER, as Chromium did. After https://boringssl-review.googlesource.com/c/boringssl/+/69508, it became a no-op even in that case too. This means, 7 years later, I can finally atone for my sins and revert the QUIC changes made in https://chromium-review.googlesource.com/c/chromium/src/+/1070648 to accommodate this mess. PiperOrigin-RevId: 745722782
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.