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

HTTP requests on one stream #692

Merged
merged 6 commits into from Jul 26, 2017
Merged

HTTP requests on one stream #692

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
eab1b26
Everything on one stream (beware HPACK)
MikeBishop Jul 19, 2017
404c5b8
Replace HPACK Sequence with zero dynamic table size
MikeBishop Jul 19, 2017
b5a4d74
Pushes aren't sequential
MikeBishop Jul 20, 2017
c2d5711
Merge remote-tracking branch 'origin/master' into one_stream
MikeBishop Jul 24, 2017
9c4eb18
SHOULD be sequential
MikeBishop Jul 24, 2017
97b5d40
utilize and reset
MikeBishop Jul 26, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 3 additions & 3 deletions draft-ietf-quic-http.md
View file
Open in desktop
Expand Up @@ -200,9 +200,9 @@ this MUST be treated as a connection error (see HTTP_MALFORMED_* in
{{http-error-codes}}). Streams which terminate abruptly may do so at any point
in 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.

It's unclear here what you mean by "terminate abruptly". Do you mean that the stream is reset, or do you mean termination in some other way?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

From the transport draft, RST_STREAM is used "to abruptly terminate a stream." Basically, I'm saying don't worry about truncated frames in the event of resets.

Copy link
Member

Choose a reason for hiding this comment

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

use the word "reset" then


Streams used for requests MUST be utilized sequentially, with no gaps. Streams
used for pushed resources MAY be initiated out-of-order, but stream IDs SHOULD
be allocated to promised resources sequentially.
Streams SHOULD be utilized sequentially, with no gaps. Streams used for pushed
Copy link
Member

Choose a reason for hiding this comment

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

https://grammarpartyblog.com/2012/01/17/use-versus-utilize/

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Not new in this PR, but sure.

resources MAY be initiated out-of-order, but stream IDs SHOULD be allocated to
promised resources sequentially.

HTTP does not need to do any separate multiplexing when using QUIC - data sent
over a QUIC stream always maps to a particular HTTP transaction. Requests and
Expand Down