users@grizzly.java.net

COMET Handler - separate threadpool, polling expiration

From: smurugu <smurugu_at_gmail.com>
Date: Mon, 7 Sep 2009 10:12:40 -0700 (PDT)

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?
- When there are too many messages queued up, does the polling feature able
to capture all expired messages on the exact expiration? 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?
- Is it possible to run the comet handler in a separate threadpool?

Thanks
Sendhil
-- 
View this message in context: http://www.nabble.com/COMET-Handler---separate-threadpool%2C-polling-expiration-tp25333691p25333691.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.