B4R Question How to reliably handle disconnects/unexpected failures with WebSockets?

ByteCounter said:

I want to create something that transfers data between B4R and B4J that doesn't require a broker

Click to expand...

You can embed the broker in the B4J app. It will be the simplest solution.

The relevant example is here: https://www.b4x.com/android/forum/threads/websocketclient.66212/
It handles the Disconnect event and tries to connect again (until successful).

@Erel thanks for the link. That example seems to be for an Arduino using the Ethernet Shield. Any chance of an ESP8266 example?

If I am using the 8266 with the Wifi to connect via WebSockets I have 2 things to worry about:
1. The WiFi could drop at any time.
2. The WebSocket connection could be interrupted.

The question is how to structure code to detect and gracefully recover from wifi and websockets disconnects/reconnects?

For Wifi I'm thinking of a Timer that fires every couple hundred milliseconds to check ESP8266WiFi.IsConnected and reattempts connection.

For WebSockets the Disconnected event code in WebSocketClient.Initialize could be used to detect connection loss. Actually now that I think about it you probably could do the Wifi check in the WebSocketClient disconnect code?

Is there anything wrong with this approach? Am I missing anything?

ByteCounter said:

Any chance of an ESP8266 example?

Click to expand...

Should be trivial to change it to work with ESP8266. Just change the client to be WiFiSocket.

Start with running the example. It handled reconnections.