Remy Maucherat wrote:
Filip Hanik - Dev Lists wrote:
Since apps are shutdown before the connectors, all CometProcessors
are marked unavailable by the time the connector wants to invoke
CometEvent.END
when thinking about it, the servlet developer can piggy back on the
Servlet.destroy method, but should we enable this call to go through
or should we remove it?
I don't think it can be called at the moment either.
I guess its useful if the connector is shutdown through JMX or other
method, but the container is still alive, so there are two ways the
CometProcessor needs to be aware of cleanup:
1. Tomcat shutdown - use CometProcessor.destroy
2. Connector shutdown - use CometEvent.END
I just noticed that CometProcessor doesn't extend HttpServlet, I thought
that inheritance was a given, is it not? It's useful for the scenario
where the connector doesn't support comet, you can still deploy and
invoke service(req,resp) method on it, and the URL is still valid.
thoughts?
Filip
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
