Hi there,
I've been developing an application which uses BlazeDS (the Adobe open
source java framework that enables developers to easily connect to back-end
distributed data and push data in real-time to flash client)
BlazeDS http-streaming channel doesn't use NIO, therefore each request uses
a new thread from the pool and sleeps on it until user disconnects.
Eventually the container thread pool would be full, and new users connecting
will have to wait.
After reading most of Jean-Francois blogs on Grizzly, I can see that Grizzly
could solve my problem, but I am not sure where and how to start.
Can Grizzly Comet solve this problem? What do you think?
Any info could help, thank you.
Hanna Haddad