Thread pool configuration

[Jeanfrancois Arcand]

Avinash Lakshman wrote:
> Here at Facebook we are experimenting with new AIO framework by trying 
> to integrate it with the Javaflow continuations. Has anyone thought 
> about this approach?

I'm currently implementing AIO support in Grizzly[1] and one of our 
module support continuation (not exactly like Javaflow). The term we are 
using is called Comet/Ajax Push (http) or Continuation (tcp). Mainly, an 
application can decide to suspend the execution of a request, and resume 
it from the same thread or from another thread, after X times.

We support such mechanism at the tcp/tls transport and also at the http 
protocol (far most popular).

A+

-- Jeanfrancois

[1] grizzly.dev.java.net



> 
> Cheers
> Avinash
> 
> On Thu, Nov 13, 2008 at 1:33 PM, Alan Bateman <Alan.Bateman at sun.com 
> <mailto:Alan.Bateman at sun.com>> wrote:
> 
> 
>     A number of people have mailed me in the last few weeks with various
>     questions on how thread pools are used by the asynchronous I/O
>     implementation. I've started a page [1] with a few notes that may be
>     useful.  When I get time I will update it with details as to how to
>     interpret thread dumps on each operating system as that is important
>     to diagnose problems (the thread dumps do vary by operating system
>     due to the differences in the I/O facilities used).
> 
>     -Alan.
> 
>     [1] http://openjdk.java.net/projects/nio/resources/AsynchronousIo.html
> 
>