Wish WebSocket Handler B4X

Erel said:

I don't think that there will be any difference between sending a ping message or sending a small text message. The length of the data sent will be the same.

Click to expand...

Jmu5667 said:

currently i have it a 50 bytes, {"type":"event","event":"c_p","params":{"X":"X"}} (this is fromt he send event to server)

Click to expand...

{"type":"ping"}

{"ping"}

{"type":"event","event":"c_p","params":{"X":"X"},"session":"SomeSortOfSessionID"}

OliverA said:

Looks like you have 10 bytes of framing per packet after a WebSocket has been initiated (see https://stackoverflow.com/a/12739418). If you think 50 bytes is too much per ping, then (if you're in control of both the client and server protocols) you could create maybe something like this

B4X:

{"type":"ping"}

which would bring you to 15 bytes and be a type that is just ignored by the server.
or

B4X:

{"ping"}

Other solution(?): Include a session parameter. This way if the connection is broken and the server sees a new WebSocket connection, it can first see if this was a previously active session and process the information accordingly. Then you would not need a ping/keep-alive mechanism. This may also cover situations where the network connection was disrupted.

B4X:

{"type":"event","event":"c_p","params":{"X":"X"},"session":"SomeSortOfSessionID"}

Update: If it is a high traffic connection with pauses now and then, I would go with the ping route. If this is a low traffic connection with pauses then I would look into implementing sessions. The session information overhead may be worth it for the high traffic connections if network interruptions are common and or can wreak havoc with your communication process.

Click to expand...

Sub send_heartbeat
 
   Dim data As Map
 
   data.Initialize
   data.Put("X", "X")
   wsh.SendEventToServer("c_p",data)
 
End Sub