bump<br><br><div class="gmail_quote">On Thu, Oct 15, 2009 at 11:10 AM, Dan D <span dir="ltr"><<a href="mailto:danotsky@gmail.com">danotsky@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
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? <br>
<br>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? <br><br>Thanks.<br><br><br><div class="gmail_quote">
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
On Tue, Sep 29, 2009 at 3:42 AM, Trustin Lee (???) <<a href="mailto:trustin@gmail.com" target="_blank">trustin@gmail.com</a>> wrote:<br>
> Hi Wade,<br>
><br>
> If your business logic takes long time, then you should use an<br>
> ExecutionHandler. ?Otherwise, other connections will freeze until the<br>
> long operation finishes. ?If there's no long operation in your<br>
> business logic, you don't usually need an ExecutionHandler in your<br>
> pipeline.<br>
><br>
> I also suggest to put decoders and encoders before ExecutionHandler<br>
> (if there is one), because decoders and encoders usually do CPU-bound<br>
> jobs.<br>
><br>
> HTH,<br>
><br>
> ? Trustin Lee, <a href="http://gleamynode.net/" target="_blank">http://gleamynode.net/</a><br>
><br></blockquote></div>
</blockquote></div><br>