Refactor BSD socket interface receive functions #18
Conversation
franz-hoepfinger-4diac
commented
Feb 22, 2024
franz-hoepfinger-4diac
commented
- Handle different error cases in receiveDataFromTCP and receiveDataFromUDP
- Log specific error messages for disconnection scenarios
- Return 0 when the connection is closed by the peer
- Handle different error cases in receiveDataFromTCP and receiveDataFromUDP - Log specific error messages for disconnection scenarios - Return 0 when the connection is closed by the peer
- Added a new method to handle errors in TCP and UDP data reception. - Updated error handling logic in receiveDataFromTCP and receiveDataFromUDP functions.
Consolidate error handling function for TCP and UDP sockets.
|
there came in some Remarks from David: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/lwip.html#bsd-sockets-api |
|
I'm now curious why we shouldn't clearly close the connection. From 4diac IDE side we definitely do that. The only problem that could arrise is that there is a timeout in 4diac IDE if the device is not responding with xxxms to close the socket on our side. But then we assume the device has died or the connection is broken (e.g., cable disconnected). As other implementations are fine with how we are interacting with 4diac FORTE I still assume it is an esp32 problem. |
|
#18 was merged and to me it seems it works very good. we lost the Error Messages here, due to the Move from Gerrit to Github: |
|
this was the Error: it is solved now. |
|
i must add here another Log, so we see how the Behaviour is on a Close of Eclipse 4diac IDE. otherwise these knowledge gets lost. |
