You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -117,7 +117,7 @@ public interface Publisher<T> {
117
117
|<a name="1.11">11</a>|A `Publisher` MAY support multiple `Subscriber`s and decides whether each `Subscription` is unicast or multicast. |
118
118
| [:bulb:](#1.11"1.11 explained") |*The intent of this rule is to give Publisher implementations the flexibility to decide how many, if any, Subscribers they will support, and how elements are going to be distributed.*|
@@ -157,7 +157,7 @@ public interface Subscriber<T> {
157
157
|<a name="2.13">13</a>|Calling `onSubscribe`, `onNext`, `onError` or `onComplete` MUST [return normally](#term_return_normally) except when any provided parameter is `null` in which case it MUSTthrow a `java.lang.NullPointerException` to the caller, for all other situations the only legal way for a `Subscriber` to signal failure is by cancelling its `Subscription`.In the case that this rule is violated, any associated `Subscription` to the `Subscriber` MUST be considered as cancelled, and the caller MUST raise this error condition in a fashion that is adequate for the runtime environment. |
158
158
| [:bulb:](#2.13"2.13 explained") |*The intent of this rule is to establish the semantics for the methods of Subscriber and what the Publisher is allowed to do in which casethis rule is violated. «Raisethis error condition in a fashion that is adequate for the runtime environment» could mean logging the error—or otherwise make someone or something aware of the situation—as the error cannot be signalled to the faulty Subscriber.*|
@@ -205,7 +205,7 @@ public interface Subscription {
205
205
206
206
A `Subscription` is shared by exactly one `Publisher` and one `Subscriber` for the purpose of mediating the data exchange between this pair. This is the reason why the `subscribe()` method does not return the created `Subscription`, but instead returns `void`; the `Subscription` is only passed to the `Subscriber` via the `onSubscribe` callback.
* Supports Publishers/Processors which do [coordinated emission](http://www.reactive-streams.org/reactive-streams-tck-1.0.2-RC1-javadoc/org/reactivestreams/tck/PublisherVerification.html#doesCoordinatedEmission--).
22
+
+ Improved JavaDoc
23
+
- Examples
24
+
+ New example [RangePublisher](http://www.reactive-streams.org/reactive-streams-examples-1.0.2-RC1-javadoc/org/reactivestreams/example/unicast/RangePublisher.html)
25
+
- Artifacts
26
+
+ NEW! [Flow adapters](#flow-adapters)
27
+
+ NEW! [Flow TCK](#flow-tck)
28
+
+ Java 9 [Automatic-Module-Name](#automatic-module-name) added for all artifacts
29
+
30
+
## Specification clarifications 1.0.2-RC1
31
+
32
+
## Subscriber Rule 2
33
+
34
+
**1.0.1:** The intent of this rule is that a Subscriber should not obstruct the progress of the Publisher from an execution point-of-view. In other words, the Subscriber should not starve the Publisher from CPU cycles.
35
+
36
+
**1.0.2-RC1:** The intent of this rule is that a Subscriber should not obstruct the progress of the Publisher from an execution point-of-view. In other words, the Subscriber should not starve the Publisher from receiving CPU cycles.
37
+
38
+
## Subscriber Rule 8
39
+
40
+
**1.0.1:** The intent of this rule is to highlight that there may be a delay between calling `cancel` the Publisher seeing that.
41
+
42
+
**1.0.2-RC1** The intent of this rule is to highlight that there may be a delay between calling `cancel` and the Publisher observing that cancellation.
43
+
44
+
## Flow adapters
45
+
46
+
An adapter library has been created to convert `org.reactivestreams` to `java.util.concurrent.Flow` and vice versa. Read more about it [here](http://www.reactive-streams.org/reactive-streams-flow-adapters-1.0.2-RC1-javadoc)
A TCK artifact has been created to allow for direct TCK verification of `java.util.concurrent.Flow` implementations. Read more about it [here](https://github.com/reactive-streams/reactive-streams-jvm/blob/v1.0.2-RC1/tck-flow/README.md)
- Added support for Publisher verification of Publishers who do coordinated emission, i.e. where elements only are emitted after all current Subscribers have signalled demand. ([#284](https://github.com/reactive-streams/reactive-streams-jvm/issues/284))
79
+
80
+
## Contributors
81
+
+ Roland Kuhn [(@rkuhn)](https://github.com/rkuhn)
82
+
+ Ben Christensen [(@benjchristensen)](https://github.com/benjchristensen)
83
+
+ Viktor Klang [(@viktorklang)](https://github.com/viktorklang)
0 commit comments