-
Notifications
You must be signed in to change notification settings - Fork 21
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
Explain emulation of partial reliability with one message per stream? #15
Comments
I think explaining how reset can create partial reliability would be useful. I think that's orthogonal to whether it's a bidirectional stream model or a message model, though. One could use partial reliability in both cases. |
Phrased as guidance on the use of resetting streams, this is useful. I don't think we're blocking on this, though, and in any case I wouldn't want whatever advice we give here to conflict with whatever partial reliability approach ends up in V2. |
Discussion in BKK seems to have converged on "don't do this for v1 applicability statement; applicability of PR and different PR strategies belongs in a document discussing PR as an extension". closing for now. |
oops, going to leave this open to track discussion. note that #54 covers an alternate view of this. |
there's a line of text in the working copy on this now: "If one message is |
No description provided.
The text was updated successfully, but these errors were encountered: