397b2a71fa
Currently, when socket errors occur during receive, the LwM2M engine restarts the state machine and registers again to the server. While this works in simple use case (only RD client socket open), it's not a valid approach when more sockets are open (FW update socket). Fix this by introducing socket fault callback, which is registered by the LwM2M engine users. This way, a proper socket owner is notified on error and can pertake appropriate action. For RD socket errors the behaviour remains the same - the state machine is reset and the client registers again to the server. For FW update socket, handle the error by reopening the socket and retransmitting the last request. This allows to resume the download from the point the error occured, w/o a need to start from scratch. Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no> |
||
---|---|---|
.. | ||
ip | ||
l2 | ||
lib | ||
buf.c | ||
CMakeLists.txt | ||
hostname.c | ||
Kconfig | ||
Kconfig.hostname | ||
Kconfig.template.log_config.default.net | ||
Kconfig.template.log_config.net |