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
Copy file name to clipboardExpand all lines: Part 4 - Concurrency/1. Scheduling and threading.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,7 @@ Finished main: 1
77
77
78
78
We see here that, not only is everything executed on the same thread, it is actually sequential: `subscribe` does not unblock until it has completed subscribing to (and thus creating) the observable, which includes executing the body of `create`'s lambda parameter. The calls to `onNext` within that lambda execute the entire chain of operators, all the way to the `println`. Effectively, subscribing on a `create`d observable is blocking.
79
79
80
-
If you uncomment `.subscribeOn(Schedulers.newThread())`, the [Output](/tests/java/itrx/chapter4/scheduling/SubscribeOnExample.java) now is
80
+
If you uncomment `.subscribeOn(Schedulers.newThread())`, the [output](/tests/java/itrx/chapter4/scheduling/SubscribeOnExample.java) now is
0 commit comments