FWIW, a colleague of mine wrote recently a nice blog post about the async HTTP processing with Grizzly 2:
http://blogs.oracle.com/oleksiys/entry/grizzly_2_0_httpserver_api1
It's worth mentioning that Grizzly powers the communication in GlassFish. IMHO the most interesting part for us is the
problem statement in the beginning of the blog, which does a good job in explaining why reusing a single container's
executor service is not a viable solution.
The blog also points at one high-performance advanced open-source executor service implementation for app developers to
use :)
I have added the blog to the references section of the async processing model wiki page.
Cheers,
Marek
On 07/20/2011 08:49 PM, Marek Potociar wrote:
> Hello experts,
>
> As announced last week, we have moved the asynchronous server-side processing API in front of some other topics in the
> schedule. I have wrote up a wiki page[1] discussing the problem domain in which I am also including some motivating
> examples, initial requirements and open topics to start the expert discussion.
>
> Please read through the wiki page[1] and send your thoughts to the EG list. Also, feel free to add new sections,
> reference links, requirements or open topics to the document, just make sure to mark the additions with your name.
>
> Let's shoot for finishing the first round of collecting the initial EG feedback on Friday (July 29) next week.
>
> Thank you,
> Marek
>
> [1] http://java.net/projects/jax-rs-spec/pages/AsyncServerProcessingModel