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

Minor mods to stream state machine text #988

Merged
merged 2 commits into from
Dec 6, 2017
Merged

Conversation

janaiyengar
Copy link
Contributor

Some rewording and added one normative.

"open" when either send or receive stream is in a non-terminal state and
"closed" when both send and receive streams are in a terminal state.
Implementations might represent the state of the bidirectional stream as a
composite of the states of the constituent send and receive streams. The
Copy link
Contributor

Choose a reason for hiding this comment

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

nits:
I a prefer lower case 'may' to 'might' in the line above.
Should it states be plural?
I think constituent is unnecessary

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

containing a previous STOP_SENDING is lost. However, once either all stream
data or a RST_STREAM frame has been received for the stream - that is, the
stream is in any state other than "Recv" or "Size Known" - sending a
STOP_SENDING frame is unnecessary.
Copy link
Contributor

Choose a reason for hiding this comment

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

Above you changed it so it's SHOULD. Should it be changed here as well?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think of this as justification for why it's a SHOULD above, so I'd prefer to leave this text as is.

Copy link
Member

Choose a reason for hiding this comment

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

SHOULD doesn't make sense here.

Copy link
Contributor Author

@janaiyengar janaiyengar left a comment

Choose a reason for hiding this comment

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

Thanks Ian, comments addressed.

"open" when either send or receive stream is in a non-terminal state and
"closed" when both send and receive streams are in a terminal state.
Implementations might represent the state of the bidirectional stream as a
composite of the states of the constituent send and receive streams. The
Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

containing a previous STOP_SENDING is lost. However, once either all stream
data or a RST_STREAM frame has been received for the stream - that is, the
stream is in any state other than "Recv" or "Size Known" - sending a
STOP_SENDING frame is unnecessary.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think of this as justification for why it's a SHOULD above, so I'd prefer to leave this text as is.

@martinthomson martinthomson merged commit 82f42f2 into master Dec 6, 2017
@martinthomson martinthomson deleted the stream-minor branch December 6, 2017 00:21
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.

None yet

3 participants