[patch] CoapUdpServer fails to include the client token in many cases

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Issue a CoAP request (with an explicit token) to a non-existent resource.

What is the expected output?
The 4.04 response should include the token option.

What do you see instead?
No token option is included, and the client does not (and should not) consider 
the response to be part of the transaction.

What version of the product are you using? On what operating system?
TinyOS-2.x trunk.

Please provide any additional information below.

Attached is a patch to include the token option with the correct value for all 
responses except CoAP ACKs to requests resulting in deferred/seperate 
responses. This should match the behavior set out in draft-ietf-core-coap-07.

Original issue reported on code.google.com by jmatts...@dius.com.au on 1 Sep 2011 at 4:16

Attachments:

• tinyos-coap-server-token.patch

[GoogleCodeExporter]

Original comment by sdh...@gmail.com on 1 Sep 2011 at 11:13

[GoogleCodeExporter]

Thomas is working on it.

Original comment by marku...@gmail.com on 16 Sep 2011 at 8:29

• Changed state: Started

[GoogleCodeExporter]

Fixed in r5759.
Thanks Steve.

Original comment by marku...@gmail.com on 20 Sep 2011 at 3:17

• Changed state: Fixed