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

Express MAX_DATA in octets rather than KB #874

Merged
merged 2 commits into from
Oct 14, 2017

Conversation

mcmanus
Copy link
Contributor

@mcmanus mcmanus commented Oct 13, 2017

closes #873

sent on the entire connection, in units of 1024 octets. That is, the updated
connection-level data limit is determined by multiplying the encoded value by
1024.
sent on the entire connection, in units octets.
Copy link
Member

Choose a reason for hiding this comment

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

of ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

imagine how many mistakes I can make in a diff more than 1 line long.

@siyengar
Copy link

wohoo

@martinthomson martinthomson merged commit 426e9ec into quicwg:master Oct 14, 2017
@siyengar
Copy link

What about initial_max_data in the extension?

@mcmanus
Copy link
Contributor Author

mcmanus commented Oct 23, 2017 via email

@siyengar
Copy link

no i'm suggesting it doesn't need to have a 1024 multiplier.

@RyanTheOptimist
Copy link
Contributor

+1! Let's just use octets.

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.

Limit MAX_DATA to the integer range (64 or 62 depending..)
5 participants