0e9fbe4a90
Currently, there are many cases where `h2` will fail a connection or stream with a PROTOCOL_ERROR, without recording why the protocol error occurred. Since protocol errors may result from a bug in `h2` or from a misbehaving peer, it is important to be able to debug the cause of protocol errors. This branch adds a log line to almost all cases where a protocol error occurs. I've tried to make the new log lines consistent with the existing logging, and in some cases, changed existing log lines to make them internally consistent with other log lines in that module. All receive-side errors that would send a reset are now logged at the debug level, using a formatting based on the format used in `framed_read`. Signed-off-by: Eliza Weisman <eliza@buoyant.io>
H2
A Tokio aware, HTTP/2.0 client & server implementation for Rust.
More information about this crate can be found in the crate documentation.
Features
- Client and server HTTP/2.0 implementation.
- Implements the full HTTP/2.0 specification.
- Passes h2spec.
- Focus on performance and correctness.
- Built on Tokio.
Non goals
This crate is intended to only be an implementation of the HTTP/2.0 specification. It does not handle:
- Managing TCP connections
- HTTP 1.0 upgrade
- TLS
- Any feature not described by the HTTP/2.0 specification.
The intent is that this crate will eventually be used by hyper, which will provide all of these features.
Usage
To use h2, first add this to your Cargo.toml:
[dependencies]
h2 = "0.1.15"
Next, add this to your crate:
extern crate h2;
use h2::server::Connection;
fn main() {
// ...
}
FAQ
How does h2 compare to solicit or rust-http2?
The h2 library has implemented more of the details of the HTTP/2.0 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.