| commit | 54648031d1d79bf618f1839d2083757b88ed865b | [log] [tgz] |
|---|---|---|
| author | Inna Palant <ipalant@google.com> | Wed Jun 12 10:54:30 2024 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Jun 12 10:54:30 2024 +0000 |
| tree | 43b0e0ebe9fbd08da77629ec30799876887b94eb | |
| parent | 98468d3d431074df5d320962f5aca564537e7e4c [diff] | |
| parent | f545393dabe5c06d69807de5189545266d722c74 [diff] |
Merge remote-tracking branch 'origin/upstream' am: f545393dab Original change: undetermined Change-Id: I7bb6bebdbc1d7d40bfc1fa4fbc1e44298b56f64d Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
A Tokio aware, HTTP/2 client & server implementation for Rust.
More information about this crate can be found in the crate documentation.
This crate is intended to only be an implementation of the HTTP/2 specification. It does not handle:
This crate is now used by hyper, which will provide all of these features.
To use h2, first add this to your Cargo.toml:
[dependencies] h2 = "0.4"
Next, add this to your crate:
extern crate h2; use h2::server::Connection; fn main() { // ... }
How does h2 compare to solicit or rust-http2?
The h2 library has implemented more of the details of the HTTP/2 specification than any other Rust library. It also passes the h2spec set of tests. The h2 library is rapidly approaching “production ready” quality.
Besides the above, Solicit is built on blocking I/O and does not appear to be actively maintained.
Is this an embedded Java SQL database engine?
No.