FWD » Core Development » User Interface

Currently there is an idle timeout for the websocket. We need to add a keep-alive sequence, otherwise a long-lived session will by automatically killed after the websocket timer pops. To recreate this today, load an application into the web client and then just let it sit there, it will disconnect automatically when the timeout occurs.

I think both the JS and Java sides should independently send a keep-alive. The other side should respond with an acknowledgement message. I think the round trip will automatically reset the websocket idle timer, so long as we send a keep-alive on a shorter time interval than the idle timer. In other words, we should calculate the keep-alive interval based on the websocket timer interval.

It is done in 1811t.