Salut,
smurugu wrote:
> Hi,
>
> I understand that the implementation of CometHandler needs to be thread
> safe, I have the following questions
>
> - Does the Comet Handler executes under HttpWorkerThread?
No.
> - When there are too many messages queued up, does the polling feature able
> to capture all expired messages on the exact expiration?
Yes.
I believe it will
> have at least 10ms+ overhead when there are too many messages are queued up.
> - Is there a way to increase the #of polling threads?
Yes, just invokes CometEngine#setThreadPool
*
http://is.gd/32uvX
> - Is it possible to run the comet handler in a separate threadpool?
Yes. Take a look at the NotificationHandler API:
*
http://is.gd/32uOv
You can write your own and plug your thread pool from there. BTW I
recommend you take a look at:
*
http://atmosphere.dev.java.net
which is Grizzly Comet.Next, and have build it for all your above
questions (and no synchronization needed).
Thanks
-- Jeanfrancois
>
> Thanks
> Sendhil