Identifying resource-using streams
Marko Topolnik
marko.topolnik at gmail.com
Tue Apr 22 15:55:19 UTC 2014
On 22. tra. 2014., at 12:41, Paul Sandoz <paul.sandoz at oracle.com> wrote:
> On Apr 21, 2014, at 10:54 PM, Marko Topolnik <marko.topolnik at gmail.com> wrote:
>
>> With lazy streams, the scope of validity of a resource stops nicely following the scope of a block of code.
>
> Yes, error handling is tricky, you may well want to react to various errors switching pipelines to return appropriate responses. It seems to me a more async/event-based stream model better fits your purpose above?
The Rx paradigm seems like a very good match, but I doubt there is a mature parallelizing implementation which I could use right now. Definitely worth investigating and keeping an eye on future developments. As far as I know, .Net already has a parallel implementation.
But more importantly, I see the need for the complete serverside stacks to support this processing model. This means that the entire stack must standardize on one approach and, naturally, I would first look to the JDK itself as the provider of that. However good or bad the fit, there will probably be attempts to use the Streams API anyway, resulting in possibly unfortunate outcomes due to the mismatch.
-marko
More information about the lambda-dev
mailing list