unfiltered.netty.cycle

Uses an ExecutorService to perform deferred tasks.

Defers all processing of the intent to a Deferral mechanism.

Defers application of the intent's response function
to a Deferral mechanism. This allows the intent to inspect
the request and potentially return Pass on the worker thread,
only deferring if it is to produce a response. The Defer
object should be used to ensure that blocking operations
are not performed in the evaluation of the intent function.

Object to facilitate Plan.Intent definitions. Type annotations
are another option.

A Netty Plan for request cycle handling.

Evaluates the intent and its response function on
an I/O worker thread. This is only appropriate if the
intent is fully CPU-bound. If any thread-blocking
I/O is required, use deferred execution.

Evaluates the intent in an unbounded CachedThreadPool
executor. For a production environment with known
memory constraints, it is better to extend
DeferralExecutor with DeferredIntent and supply
a configured MemoryAwareThreadPoolExecutor.