>
> 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.
Please take a look here:
http://docs.sun.com/app/docs/doc/820-4496/ggrgy http://docs.sun.com/app/docs/doc/820-4496/ghgxk?a=view
> Can Grizzly Comet solve this problem? What do you think?
I think it's exactly what you need. Grizzly Comet leverages all
advantages of Java NIO and provides HTTP push functionality.
Thanks.
WBR,
Alexey.
>
>
> Any info could help, thank you.
>
> Hanna Haddad