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
That just bemuses me. Why am I getting an infinite stream of ones for the first observable, but for the others it seems OK. And I'm not even sure that the behavior of others is what I'd expect according to the documentation stating that publishReturns a rx.lang.scala.observables.ConnectableObservable, which waits until the connect function is called before it begins emitting items from this rx.lang.scala.Observable to those rx.lang.scala.Observers that have subscribed to. It probably is OK, it is just that I'm not able to deduce from that documentation that publish is somehow internally keeping track of which items from the published observable have already been emitted and which not even in case of resubscribing to it multiple times...
Can someone enlighten me on this, please?
The text was updated successfully, but these errors were encountered:
RxScala 0.23.1 (that means RxJava 1.0.4)
gives me
That just bemuses me. Why am I getting an infinite stream of ones for the first observable, but for the others it seems OK. And I'm not even sure that the behavior of others is what I'd expect according to the documentation stating that
publish
Returns a rx.lang.scala.observables.ConnectableObservable, which waits until the connect function is called before it begins emitting items from this rx.lang.scala.Observable to those rx.lang.scala.Observers that have subscribed to. It probably is OK, it is just that I'm not able to deduce from that documentation thatpublish
is somehow internally keeping track of which items from the published observable have already been emitted and which not even in case of resubscribing to it multiple times...Can someone enlighten me on this, please?
The text was updated successfully, but these errors were encountered: