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
{{ message }}
This repository has been archived by the owner on Apr 20, 2018. It is now read-only.
Since down stream operators won't have control of this, I am thinking it should be built into the operator, so either:
varpauser=Rx.Observable.just(true).delay(400);//Pass in an observable and pause the stream on truthy values and resume on falsey (or vice versa)Rx.Node.fromReadableStream(stream,pauser);
or take the backpressure/connect approach
varpausableObservable=Rx.Node.fromReadableStream(stream);//It is now pausedvardisposable=pausableObservable.pause();//It is now unpauseddisposable.dispose();
Personally I tend toward the first, since the second might have some confusing semantics for some people, and in general it forces yet another chain break. But I don't generally use this method so I would leave it up to people like @hekike .
This issue is moved from: Reactive-Extensions/RxJS#508
http://nodejs.org/api/stream.html#stream_readable_pause
I tried to request only two items from a Readable Node stream with
Rx
and I observed the following behaviour:Rx subscribe
next emits only the expected two itemsRx Observable
reads every item from the stream, doesn't pause the stream after twoRx
or
I think Rx should support some backpressure here and pause the Readable stream. Would be great for
take
also.In Highland it works in the following way:
Did I miss something?
The text was updated successfully, but these errors were encountered: