commit | 13074419cdd890bfe67fbba70e70857375a1eb9f | [log] [tgz] |
---|---|---|
author | QUICHE team <quiche-dev@google.com> | Thu Dec 16 12:40:23 2021 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Dec 16 12:41:49 2021 -0800 |
tree | 7c9cb3a509a3dafe26f153df58df1b83ded64f4a | |
parent | ed970f7c38381309e9306982efa8dcfac1201269 [diff] |
Refactor OgHttp2Session::ProcessBytes(). This CL adds internal OgHttp2Session::ProcessBytesImpl() that returns an absl::variant that contains either the number of bytes processed on success or an error code on failure. Then ProcessBytes() calls ProcessBytesImpl() and returns an overall int based on the absl::variant. This CL is a pure refactoring CL with only one error code at the moment, but the error codes will grow in a future CL to include values compatible with nghttp2. This compatibility will be useful for some codec_impl_test tests. PiperOrigin-RevId: 416872938
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.