Expand description
Asynchnous HTTP/2 client and server implementation.
Based on futures/tokio.
This crate is used to implement grpc
crate,
and probably not usable for anything else.
Structs§
- Bytes
Deque VecDeque<Bytes>
but slightly more efficient.- Client
- Asynchronous HTTP/2 client.
- Client
Builder - Builder for HTTP/2 client.
- Client
Conf - Client configuration.
- Client
Request - Reference to outgoing stream on the client side.
- Header
- HTTP/2 header, regular or pseudo-header
- Header
Name - Representation of header name
- Header
Value - A convenience struct representing a header value.
- Headers
- HTTP message headers (or trailers)
- Http
Stream After Headers - Stream of DATA or HEADERS frames after initial HEADERS.
- Response
- Convenient wrapper around async HTTP response future/stream
- Server
- Server
Builder - Server
Conf - Server
Handler Context - Server
Handler Paths - Convient implementation of
ServerHandler
which allows delegation to multipleServerHandler
implementations provided by user. - Server
Increase InWindow - Server
Request - Server
Response - Simple
Http Message
Enums§
- AnySocket
Addr - Client
TlsOption - Data
OrTrailers - Stream frame content after initial headers
- Error
- An enum representing errors that can arise when performing operations involving an HTTP/2 connection.
- Error
Code - The enum represents an error code that are used in
RST_STREAM
andGOAWAY
frames. These are defined in Section 7 of the HTTP/2 spec. - Http
Scheme - An enum representing the two possible HTTP schemes.
- Pseudo
Header Name - HTTP/2 pseudo header name.
- Send
Error - Sender
State - Server
Alpn - Server
TlsOption - Stream
Dead
Traits§
- BufGet
Bytes - Get
Bytes
fromBuf
. - Client
Interface - Server
Handler - Central HTTP/2 service interface.
- Server
Request Stream Handler - Synchronous callback of incoming data