Cancelable streams (original) (raw)
Joe Bowbeer joe.bowbeer at gmail.com
Sun Nov 4 20:30:22 PST 2012
- Previous message: Cancelable streams
- Next message: Cancelable streams
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Plus, the ability to query the gate to determine whether the pipeline finished because it was out of elements, or because the gate was manually closed.
In my view, closing the gate doesn't "finish" the stream, it just stalls it. Gates open and close. They can be used to delay the start until the appointed time, regulate the passage of elements, pause, resume, etc.
On Sun, Nov 4, 2012 at 8:13 PM, Brian Goetz <brian.goetz at oracle.com> wrote:
> In essence I think you want to insert a "gate" operation into the pipeline - while the gate is open elements can be read from the stream, but when it is closed they can not. The question then becomes how you control the gate, either from within the pipeline (predicate based) or externally (time-trigerred callback).
Yes, that is exactly what I am suggesting. Plus, the ability to query the gate to determine whether the pipeline finished because it was out of elements, or because the gate was manually closed.
- Previous message: Cancelable streams
- Next message: Cancelable streams
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the lambda-libs-spec-observers mailing list