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

Dmitri is the mystery speaker concerned about tracking each byte #15

Merged
merged 1 commit into from Oct 30, 2017
Merged

Dmitri is the mystery speaker concerned about tracking each byte #15

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.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion interim-17-10/minutes.md
View file
Open in desktop
Expand Up @@ -935,7 +935,7 @@ Jana: agrees that this callback would be incredibly useful. He also notes that

Jeff: it actually gets used fairly frequent, as things move into and out of the table; eviction is frequent.

Speaker: acknowledging a range of bytes means that there is a degenerate case in which you might have to track each byte.
Dmitri: acknowledging a range of bytes means that there is a degenerate case in which you might have to track each byte as data may be reframed during retransmission. This is too much to ask of a generic transport protocol just to support one use case (HTTP).

Jeff asks what the second disagreement is? Stream reset is mitigated. (Jana notes that eviction may be less common for single server cases)

Expand Down