Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Talk about concurrency in H3 vs. H2 #3114

Merged
merged 4 commits into from
Oct 29, 2019
Merged

Talk about concurrency in H3 vs. H2 #3114

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
1705a15
Talk about concurrency
MikeBishop Oct 17, 2019
8ceca2a
Talk about push separately
MikeBishop Oct 18, 2019
ad5ed87
Precision, thanks to @kazuho
MikeBishop Oct 18, 2019
ca1c494
Update draft-ietf-quic-http.md
MikeBishop Oct 18, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions draft-ietf-quic-http.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1814,6 +1814,22 @@ considerations about exhaustion of stream identifier space apply, though the
space is significantly larger such that it is likely that other limits in QUIC
are reached first, such as the limit on the connection flow control window.

In contrast to HTTP/2, stream concurrency in HTTP/3 is managed by QUIC. QUIC
considers a stream closed when all data has been received and sent data has been
acknowledged by the peer. HTTP/2 considers a stream closed when the frame
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this sentence is incorrect.

I think it should be: "QUIC considers a stream closed when all data have been received and all the sent data have been acknowledged."

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or a reset has been sent and acknowledged.

containing the END_STREAM bit has been committed to the transport. As a result,
the stream for an equivalent exchange will typically remain "active" for one
additional round trip. HTTP/3 servers might choose to permit a larger number of
concurrent client-initiated bidirectional streams to achieve equivalent
concurrency than were permitted in HTTP/2, depending on the expected usage
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"permit a larger number...than were permitted" makes sense, but there are so many words between them that it's kind of hard to parse.

Copy link
Contributor

@ianswett ianswett Oct 21, 2019 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
concurrency than were permitted in HTTP/2, depending on the expected usage
concurrency to HTTP/2, depending on the expected usage

patterns.

Due to the presence of other unidirectional stream types, HTTP/3 does not rely
exclusively on the number of concurrent unidirectional streams to control the
number of concurrent in-flight pushes. Instead, HTTP/3 clients use the
MAX_PUSH_ID frame to control the number of pushes received from an HTTP/3
server.

## HTTP Frame Types {#h2-frames}

Many framing concepts from HTTP/2 can be elided on QUIC, because the transport
Expand Down