6 years, 5 months ago.

Client cycle

Hello, when calling Yeld, with socket timed out, the cycle function detects negative values from socket recv as an error and 0 as socket timeout (see code fragment below):

int packet_type = readPacket(timer); read the socket, see what work is due

switch (packet_type) { default: no more data to read, unrecoverable. Or read packet fails due to unexpected network error rc = packet_type; goto exit; case 0: timed out reading packet break;

While the Mbed recv specs says: "By default, recv blocks until data is sent. If socket is set to non-blocking or times out, NSAPI_ERROR_WOULD_BLOCK is returned immediately."

So, in the case of socket time out, the returned value, if the brocker has nothing to send, will be NSAPI_ERROR_WOULD_BLOCK wich is not an error but just an indication of no incoming data. Unfortunatly the readPacket interpret it as an error causing the MQTT client to close the connection. Is this the correct behaviour? Thank you, best regards

Question relating to:

MQTT

Deprecated This team is no longer maintained, please use: https://github.com/ARMmbed/mbed-mqtt instead.