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.

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

Enabling the use of PRIORITY at any time #643

Merged
merged 3 commits into from
Nov 22, 2014
Merged

Conversation

martinthomson
Copy link
Collaborator

As discussed on the mailing list.

Closes #642.

@igrigorik
Copy link
Member

👍

@@ -4735,6 +4744,12 @@ HTTP2-Settings = token68
This section is to be removed by RFC Editor before publication.
</t>

<section title="Since draft-ietf-httpbis-http2-14" anchor="changes.since.draft-ietf-httpbis-http2-15">
Copy link
Contributor

Choose a reason for hiding this comment

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

I think you mean "since -15"

applied, endpoints SHOULD maintain state for at least as many streams as allowed by
their setting for <x:ref>SETTINGS_MAX_CONCURRENT_STREAMS</x:ref>.
Similarly, streams that are in the "idle" state can be assigned priority or become a
dependency for other streams. This allows for the creation of a grouping node in the
Copy link
Contributor

Choose a reason for hiding this comment

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

s/become a dependency for other streams/become the parent of other streams/.
I thinks this better fit the terminology we decided to use for priorities.

@martinthomson martinthomson merged commit 84af05b into master Nov 22, 2014
@martinthomson martinthomson deleted the priority_idle branch November 25, 2014 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow PRIORITY on stream in any state
4 participants