Inconsistency when sendto returns an error

Status: Beta

Brought to you by: obgm

This project can now be found here.

#8 Inconsistency when sendto returns an error

Status: closed-fixed

Owner: Olaf Bergmann

Labels: None

Priority: 5

Updated: 2012-06-29

Created: 2012-06-27

Creator: John Sucaet

Private: No

if sendto (called in coap_send_impl) returns an error (0 bytes written), coap_send_confirmed will return COAP_INVALID_TID. This signals the calling function that the pdu can be discarded due to transmission errors. However coap_send_confirmed has appended this pdu to the send queue for retransmission.

Attached a proposal for fixing this.

Discussion

John Sucaet - 2012-06-27

fix-sendto.patch

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Olaf Bergmann - 2012-06-29

assigned_to: nobody --> obgm

status: open --> closed-fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Olaf Bergmann - 2012-06-29

Fixed by applying your patch, thanks.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Inconsistency when sendto returns an error

Group

Searches

Help

#8 Inconsistency when sendto returns an error

Discussion