Francesco Di Muccio

Yes, as stated in the link that you posted the only way to detect a broken TCP connection is trying to send some bytes. In SockJSSettings there is an option...

By the way it could be fixed by implementing a ping/pong style heartbeat, but unluckily SockJS protocol does not support it natively, so you need to implement it at higher...

I tested it further and it does detect disconnect, but it does after enough data has been transferred, so I guess there is some internal buffer and timeout that control...

Hi, unluckily it is not compatible with Akka Cluster yet. I'm planning to add support for it, but it requires a major rework of the internals. I don't have yet...

Hi, sorry for the delay. I removed all API that were deprecated in 0.5. `SockJS.withActor` was returning a `SockJS` implementation based on callback, both have been replaced by an API...

Yes, one goal of this project is to have a set of api that mirror the one provided by Play. In this way it is straightforward to switch from Play...

Hi, some overhead must be taken into account when using SockJS. Everytime a message is received or sent from ws (or wss) it must be deserialized or serialized from/to json...

I see, so you are using the raw websocket transport (without SockJS framing), in this case the performance should be very close to the native Play plain websockets (no json...