Hi Minh,
Minh O wrote:
> So I thought that might be the case in that regards but the hashcode is correct because I print the hashcode on handler add and the hashcode on message send and they both match up. I'll do more testing tonight to see if I made a mistake because that is a likely candidate so hopefully I find something tonight.Also, do I need the "event.getCometContext().resumeCometHandler(this);"
You only need to invoke the resumeCometHandler if you want to resume the
suspended connection. That might be the problem then...usually, you
suspend the connection by calling addCometHandler(), and resume it using
resumeComentHandler(). Do you need to resume it or can it be expired by
Grizzly itself using the CometContent.setExpirationDelay() value?
in the handler because from looking at the code it removes it from the
map?ThanksMinh>
Yes you are right. So you probably don't want to call it :-)
Thanks
-- Jeanfrancois