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

Describe the impact of priority on other connections #105

Closed
wants to merge 1 commit into from
Closed

Describe the impact of priority on other connections #105

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
12 changes: 12 additions & 0 deletions draft-kazuho-httpbis-priority.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -240,6 +240,18 @@ compatible for peers that are unaware of the extended meaning.
The scheme has a single encoding and set of functionality whether it's
conveyed via a HTTP header or within a frame.

## Impact on other connections
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
## Impact on other connections
## Impact on Other Connections


When multiple connections are open, the priority MAY have impact on the
Copy link
Collaborator

Choose a reason for hiding this comment

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

For my own benefit at least, I would like to understand what exactly "multiple connections" means in this context. There is a difference to multiple HTTP connections to the same authority (something not recommended for H2 or H3) vs multiple connections to different authorities that all compose a page (but are serviced by the same physical machine) vs just the client having multiple TCP connections open .

client's local scheduling choices, but MUST NOT change how the server allocates
resources among different incoming connections unless it has a guarantee some
set of connections are from the same client. When a server knows multiple
incoming connections are from the same client, the server MAY use the priority
to inform scheduling decisions among the client's different connections.

Due to this, priority information conveyed over a non-coalesced HTTP
connection might go unused.

# The Priority HTTP Header Field

The Priority HTTP header field can appear in requests and responses. A client
Expand Down