search

ibm-security-innovation / crosscoap

CoAP-to-HTTP translator proxy
https://developer.ibm.com/open/crosscoap/
Apache License 2.0
66 stars 22 forks source link

Blockwise Transfers #1

Open bsmelo opened 7 years ago

bsmelo commented 7 years ago

Regarding the following note from README.md:

CoAP is UDP-based, and therefore the entire CoAP message (UDP headers, CoAP headers and CoAP payload) must fit in the network MTU, which is generally around 1500 bytes. If the response body from the HTTP server is too long, crosscoap will truncate it (and log an error). Keep the HTTP response body under 1400 bytes to be safe.

This is exactly the kind of thing which can be solved by Blockwise Transfers [1], right?

I see that go-coap still does not implement this RFC, though there is an issue open for this at dustin/go-coap#26. Maybe this can be an enhancement for crosscoap as well?

[1] https://tools.ietf.org/html/rfc7959

dubek commented 7 years ago

Thank you for the suggestion. All CoAP implementation details should go into go-coap. Once it is supported in go-coap I believe it would be simple to enable blockwise transfers for CoAP requests originated by crosscoap (that is, responses to the CoAP client).