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

State bikeshedding time #520

Closed
martinthomson opened this issue May 11, 2017 · 5 comments
Closed

State bikeshedding time #520

martinthomson opened this issue May 11, 2017 · 5 comments
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.

Comments

@martinthomson
Copy link
Member

"half-closed (local)" might be a little obtuse. "write-closed" or "read-only" might be better names.

Release the hounds.

@martinthomson martinthomson added editorial An issue that does not affect the design of the protocol; does not require consensus. -transport labels May 11, 2017
@LPardue
Copy link
Member

LPardue commented May 11, 2017

Would these states become redundant if the "unidirectional streams" concept takes foot

@MikeBishop
Copy link
Contributor

Somewhat. If the unidirectional flavor is pairs of unidirectional streams, these could be defined shorthand for the state of a pair. If it's completely independent streams in each direction, yes, they're obsolete.

@ianswett
Copy link
Contributor

I think Martin's inflight #894 will solve this issue.

@MikeBishop
Copy link
Contributor

Yes, but the corollary on frame names is still there.... RST_STREAM => WRITE_ABORT, STOP_SENDING => READ_ABORT make even more sense after #894.

@martinthomson
Copy link
Member Author

Fixed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
None yet
Development

No branches or pull requests

4 participants