continued from: https://b4x.com/android/forum/threads/error-log-in-b4r-astreams-client-server-tutorial.108554/
Erel had explained that with B4R Astreams, astream_Error is raised when the connection is broken.
Using the code from: https://www.b4x.com/android/forum/threads/connecting-two-esp8266-boards.89726/#content but with the server.Socket.Close statement removed:
I assumed that removing the .close statement would leave the connection in tact, which it does. But I also assumed that in that state removing the power from the device at one end would break the connection and produce an error at the other.
Removing the power at the server end does, indeed, produce an error at the client end.
But, removing the power at the client end doesn't give any error at the server end, even after many minutes. Further, on re-connecting the power at the client end, the client tries to connect and write and, apparently, succeeds but nothing happens at the server end.
Erel had explained that with B4R Astreams, astream_Error is raised when the connection is broken.
Using the code from: https://www.b4x.com/android/forum/threads/connecting-two-esp8266-boards.89726/#content but with the server.Socket.Close statement removed:
I assumed that removing the .close statement would leave the connection in tact, which it does. But I also assumed that in that state removing the power from the device at one end would break the connection and produce an error at the other.
Removing the power at the server end does, indeed, produce an error at the client end.
But, removing the power at the client end doesn't give any error at the server end, even after many minutes. Further, on re-connecting the power at the client end, the client tries to connect and write and, apparently, succeeds but nothing happens at the server end.