WebSDK significantly expands the WE possibilities.
It is even possible to work only with the WebSDK.
In this case, it is sometimes interesting that the framework does not close the client side when the communication with the server is turned off.
Indeed, with the WebSDK, it is possible to have a virtually autonomous page (in the browser).
For example, if we had a ‘server not available’ browser event, we may decide to close the client side (as now) or not (and in this case, it would be up to us to deal with the fact that the client side can not communicate with our server app, temporarily or not).
It would be a big breakthrough!
Note: We already have the “disconnect” event, but works in the other direction: Notify the server that the client is closed.