When is ExecutionHandler necessary

[Dan D]

Below, Trustin mentions using an ExecutionHandler for long-running business
logic to prevent tying up Netty's worker threadpool.  If a cached thread
pool is being used for the worker threads, is this still a problem?  Won't
the threadpool just expand as necessary if business logic is tying up
threads?

Also is an ExecutionHandler required, or can we just submit work to our own
ExecutorService?  If ExecutionHandler isn't required, what are the benefits
to using one?

Thanks.



> On Tue, Sep 29, 2009 at 3:42 AM, Trustin Lee (???) <trustin at gmail.com>
> wrote:
> > Hi Wade,
> >
> > If your business logic takes long time, then you should use an
> > ExecutionHandler. ?Otherwise, other connections will freeze until the
> > long operation finishes. ?If there's no long operation in your
> > business logic, you don't usually need an ExecutionHandler in your
> > pipeline.
> >
> > I also suggest to put decoders and encoders before ExecutionHandler
> > (if there is one), because decoders and encoders usually do CPU-bound
> > jobs.
> >
> > HTH,
> >
> > ? Trustin Lee, http://gleamynode.net/
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/netty-users/attachments/20091015/11915d40/attachment.html