Skip to content

remove unnecessary Processor rules #69

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

Closed
rkuhn opened this issue Jun 14, 2014 · 9 comments
Closed

remove unnecessary Processor rules #69

rkuhn opened this issue Jun 14, 2014 · 9 comments

Comments

@rkuhn
Copy link
Member

rkuhn commented Jun 14, 2014

4.2 (cancel upstream after last downstream has canceled) and footnote 1 (must be prepared to start receiving before there are downstream subscribers) are not needed as the behavior is sufficiently specified by the provisions of 4.1 and 4.3.

@benjchristensen
Copy link
Contributor

Conversation: #61 (comment)

About this:

+| 2 | A Processor MUST cancel its upstream Subscription if its last downstream Subscription has been cancelled |

@benjchristensen
Copy link
Contributor

#61 (comment)

+[1] A Processor must be prepared to receive incoming elements from its upstream even if a downstream subscriber has not requested anything yet.

@viktorklang
Copy link
Contributor

👍

@viktorklang
Copy link
Contributor

Others? @reactive-streams/contributors

@smaldini
Copy link
Contributor

👍

@viktorklang
Copy link
Contributor

Time to finalize the votes, if you need more time, please respond here with how much time (reasonable) is needed to cast your vote. @reactive-streams/contributors

@tmontgomery
Copy link

👍

@DougLea
Copy link
Contributor

DougLea commented Jul 7, 2014

Sorry for delay. I think it is in as good shape as it needs to be :-)

@benjchristensen
Copy link
Contributor

Agreed with removal of 4.2 and footnote 1.

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

No branches or pull requests

6 participants