| commit | b2ab503e6b42963f15fb4490608a44cb807e2eb1 | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Thu Mar 03 07:48:26 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Mar 03 07:49:09 2022 -0800 |
| tree | 28addb28b11abd5b23106a74f4a302068f2763fc | |
| parent | fc8bb9929a4e413eb91b2e0a029328fb779b67e4 [diff] |
Automated g4 rollback of changelist 432178898. *** Reason for rollback *** TAP has detected 10 or more targets failed to build at cl/432178898. TO ROLLFORWARD (without additional approval): Use go/undo-autorollback and consider filing a go/autorollback-bug. To see all broken targets visit http://test/432178898 or go/newly-broken?p=cl:432178898 if the former is slow to load. To prevent noise from flakes, TAP double-checked the following target fails to build: http://sponge2/label%3Atap%20label%3Apostsubmit%20cl%3A432178898%20target%3A%2F%2Fthird_party%2Farcore%2Fjava%2Fcom%2Fgoogle%2Far%2Fcore%3AARCore_arm_32_security_test_audit_android_security but used to build fine: http://sponge2/label%3Atap%20label%3Apostsubmit%20cl%3A432178897%20target%3A%2F%2Fthird_party%2Farcore%2Fjava%2Fcom%2Fgoogle%2Far%2Fcore%3AARCore_arm_32_security_test_audit_android_security Questions? Comments? See the URL: go/autorollback *** Original change description *** Simplify QuicStreamSendBuffer::SaveStreamData(). This method is called at two places in production: QuicCryptoStream::WriteCryptoData() and QuicStream::WriteOrBufferDataAtLevel(), both times with an iovec created locally from an absl::string_view. In order to reduce complexity, this CL changes SaveStreamData() to take an absl::string_view directly instead of an iovec. *** PiperOrigin-RevId: 432192634
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.