Clarified the expected behaviour for triggerRequest #442
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This addresses some of the problem raised in reactive-streams#280.
viktorklang
reviewed
Nov 19, 2018
| * <p> | ||
| * Before sending any element to the subscriber, the TCK must wait for the subscriber to request that element, and | ||
| * must be prepared for the subscriber to only request one element at a time, it is not enough for the TCK to | ||
| * simply invoke this method before sending elements. |
There was a problem hiding this comment.
Has the following semantics been verified throughout the TCK now? (So that the TCK uses the method appropriately, as described)
There was a problem hiding this comment.
Yes, I believe it has.
|
Thanks @jroper! 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This addresses some of the problem raised in #280.