Consider me poked!
So, the Java answer to "how do I run things in multiple threads" is to
use an Executor (java.util). This doesn't necessarily mean that you
*have* to use a separate thread (the implementation could execute
inline). However, in order to accommodate the separate thread case,
you would need to code to a Future-like API. Now, I'm not saying to
use Executors directly, but I'd provide some abstraction layer above
them or in lieu of them, something like:
public interface ExecutorThingy {
Future<T> execute(Function<T> fn);
}
One could imagine implementing different ExecutorThingy
implementations which allow you to parallelize things in different
ways (simple threads, JMS, Akka, etc, etc.)
On Wed, Apr 15, 2015 at 10:33 AM, Phil Steitz <phil.ste...@gmail.com> wrote:
> James Carman and I had a brief conversation following my Apachecon
> talk, where I mentioned the challenge we have around deciding what
> to do about supporting multiple threads / processes. He has some
> good ideas. This is really just a poke to get him to post those
> ideas :)
>
> The final presented slides are here:
> http://s.apache.org/arB
>
> Thanks for the feedback as I was preparing!
>
> Phil
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
