Uh oh!
There was an error while loading. Please reload this page.
Operation throttleLast - #365
Conversation
…ationThrottle class.
…xJava into throttle-merge Conflicts: rxjava-core/src/main/java/rx/Observable.java rxjava-core/src/main/java/rx/concurrency/TestScheduler.java
cloudbees-pull-request-builder
commented
Sep 10, 2013
RxJava-pull-requests #258 SUCCESS |
benjchristensen
commented
Sep 10, 2013
NOTE: This implementation is modified to use As currently implemented this returns the last value of each I'm curious about when the different types of implementations may be more valuable than others. |
samuelgruetter
commented
Sep 10, 2013
Great! Looking forward to having this operator :) |
benjchristensen
commented
Sep 10, 2013
This will return the last value in each time window. It will always emit at least 1 value in each window. PublishSubject<Integer> o = PublishSubject.create();
o.throttleLast(500, TimeUnit.MILLISECONDS, s).subscribe(observer);
// send events with simulated time incrementss.advanceTimeTo(0, TimeUnit.MILLISECONDS);
o.onNext(1); // skipo.onNext(2); // delivers.advanceTimeTo(501, TimeUnit.MILLISECONDS);
o.onNext(3); // skips.advanceTimeTo(600, TimeUnit.MILLISECONDS);
o.onNext(4); // skips.advanceTimeTo(700, TimeUnit.MILLISECONDS);
o.onNext(5); // skipo.onNext(6); // delivers.advanceTimeTo(1001, TimeUnit.MILLISECONDS);
o.onNext(7); // delivers.advanceTimeTo(1501, TimeUnit.MILLISECONDS);
o.onCompleted();Compare this with #366 |
benjchristensen
commented
Sep 10, 2013
Please review this behavior and let me know if it is accurate and if the name is explanatory. |
benjchristensen
commented
Sep 10, 2013
Javadoc:
|
benjchristensen
commented
Sep 10, 2013
I have submitted 3 separate pull requests with different variants of
Variants are:
|
DavidMGross
commented
Sep 10, 2013
Would you summarize for me how this differs from sample()? On Tue, Sep 10, 2013 at 12:17 AM, Ben Christensen
|
benjchristensen
commented
Sep 10, 2013
The |
Merge of #258