Introduce HTTP/2 API to batch frames #3766
Assignees
Labels
Comments
sbordet
added a commit
that referenced
this issue
Sep 1, 2020
Introduced Stream.FrameList to hold HEADERS+DATA+HEADERS frames. These are often used by the client and by the server when the request/response content is known and FrameList will allow to send them in a single TCP write, rather than multiple ones. Rewritten HttpSenderOverHTTP2.sendHeaders() and HttpTransportOverHTTP2.sendHeaders() to take advantage of FrameList. Now using ConcurrentHashMap as a client context, because with DEBUG logging enabled it may be access concurrently. Signed-off-by: Simone Bordet <[email protected]>
sbordet
added a commit
that referenced
this issue
Sep 1, 2020
Fixed HttpTransportOverHTTP2.sendHeaders() - HEADERS frame for trailers was missing the stream id. Signed-off-by: Simone Bordet <[email protected]>
sbordet
added a commit
that referenced
this issue
Sep 9, 2020
Updates after review. Signed-off-by: Simone Bordet <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be great if we had a HTTP/2 API to batch multiple frames with a single callback.
This is necessary for example to send request + data, or data + trailers, while currently these operations must be performed individually and may result in multiple TCP writes.
See for example
HttpSenderOverHTTP2.The text was updated successfully, but these errors were encountered: