Alexi,
As discussed in the call,
- Is it possible to have a separate thread pool for Servlet Container. The
reason being any malformed request or longer running request on the servlet
could potentially block the incoming connections because one common thread
pool is used. I would even prefer to have a separate thread pool per servlet
if possible
- I wan to recieve the request on Consumer servlet and dispatch the request
to another thread (separate thread pool) and process the request
asynchronously without blocking the consumer thread. There are 2 options
discussed: ARP & Comet. Could you please provide some examples on ARP &Comet
- Provide some pointers on integrating JAX-WS servlet into Grizzly
Thanks
Sendhil
Oleksiy Stashok wrote:
>
> Agenda:
>
> + Grizzly 1.9.x updates: 1.9.18 release
> + Grizzly servlet container
> + Grizzly 2.0 updates
> + round table
>
>
> Logistics:
> Time: 10:00am Pacific Time, Noon Central Time, 13:00 Eastern Time,
> 19:00 CET
> Toll free: 866.692.3163
> International: 1.203.418.3122
> Access code: 6454223
>
> Every one is welcome!
>
> WBR,
> Alexey.
>
>
--
View this message in context: http://www.nabble.com/Project-Grizzly-Meeting-Agenda-%28September-2%2C-2009%29-tp25259401p25262287.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.