Here is the use case: we make these endpoints go through the javee instance manager. Being a ee server we support @Inject and in some cases - sadly the most common one - we need a cleanup hook once the endpoint is no more used.
Strictly at tomcat level think to postconstruct/predestroy support for instance. Side note: when i spoke about timeout i thought to WsTimeout. Main point is to know when to release the instance. Note also it would be awesome to have it for tomcat 8 :). Le 4 nov. 2015 00:57, "Rémy Maucherat" <r...@apache.org> a écrit : > > 2015-11-04 9:47 GMT+01:00 Mark Thomas <ma...@apache.org>: > > > On 04/11/2015 06:28, Romain Manni-Bucau wrote: > > > Hi guys, > > > > So you only want the views of the male committers? > > > > > Would it be possible to add to tomcat codebase a way to register custom > > > websocket lifecycle listeners for technical integration. For instance in > > > TomEE we would need a clean way to listen for close() or timeout() > > without > > > modifying the user code side if possible. > > > > Why? What is the use case? > > > > Also, there is no timeout() method but there is an error() method. There > > is no clear way to differentiate between timeout and any other errors. > > > > > wdyt? > > > > Looking at trunk, it appears to be doable with some refactoring but > > there would be a (probably small) performance impact. It depends on the > > justification. > > > > Maybe it could be the usual integration thing, for example at the moment > the endpoint instances are not going through the InstanceManager. Not sure > if that would be enough for him. Obviously a listener system would be much > more annoying (configuration needed, etc ...). > > Rémy
