Hi Dejan, I don't have much of an idea how Jetty handles the websocket protocol. Maybe it would be easier to make some configurable hook, so that you can for example plug in a netty websocket server where all events are readily available. If they are available in Jetty, too they should definitely be exposed, maybe by way of a configurable Listener which you can hook in.
Problem with websocket protocol is that the connection is reestablished with a new connection id when the user for example reloads the page, so there should also be some access to the connected users which should be identifiable. Most problems can be solved without any problem with establishing queues or topics for individual users or user groups (think IRC like systems) but a lot of messages could be lost or lingering when they are sent though a user is already disconnected. Regards, Otho Am 1. März 2012 16:31 schrieb Dejan Bosanac <[email protected]>: > Hi Otto, > > it doesn't seem possible at the moment. Every contribution is more than > welcomed :) > > Regards > -- > Dejan Bosanac > Senior Software Engineer | FuseSource Corp. > [email protected] | fusesource.com > skype: dejan.bosanac | twitter: @dejanb > blog: http://www.nighttale.net > ActiveMQ in Action: http://www.manning.com/snyder/ > > > > On Thu, Mar 1, 2012 at 2:24 PM, Otho <[email protected]> wrote: > > > Hi all! > > > > It there any possibility to get notified on close of a WebSocket > > connection? > > > > The ServerSocket onClose method contains no logic and interceptors don't > > seem to offer that functionality, too. > > > > Regards, > > Otho > > >
