Reactive Microserver : Make simple-react available on Rest resource handlers about micro-server HOT 2 CLOSED

I think the following options would be useful

single-threaded (optionally non blocking)

sync synchronous execution of a FutureStream, but not on the calling thread (i.e. can be non-blocking to the calling thread via the run method). Would get it's own thread to execute on from a pool.

possibly cpuSync synchronous execution of a FutureStream on a single thread, but not on the calling thread, using common ForkJoinPool (or same Thread pool as cpuStream) see below

multi-threaded (optionally non blocking)

IOStream for creating IO bound Streams. The first action would be async (i.e. tasks passed to task executor), subsequent tasks would execute synchronously on the calling thread. Note the first action doesn't have to be IO related, the first stage being async distributes the work to separate workers. Users can manually change this behaviour via async / sync operators on FutureStreams. (Can be non-blocking to the calling thread)

cpuStream for creating CPU bound streams, would probably reuse the common ForkJoinPool, first action would be async (i.e. tasks passed to a task executor to distribute the work load), subsequent tasks would execute synchronously on the calling thread. Users can manually change this behaviour via async / sync operators on FutureStreams. (Can be non-blocking to the calling thread)

switchIO could be used to switch a Stream optimised for CPU bound execution into one optimised for IO Bound execution

switchCPU could be used to switch a Stream optimised for IO bound execution into one optimised for CPU Bound execution

from micro-server.

Available on Master

from micro-server.