[riot-notifications] [RIOT-OS/RIOT] net/nanocoap: write struct-based block1 option (#10702)

Ken Bannister notifications at github.com
Sat Jan 5 14:57:46 CET 2019


This PR unfortunately was premature. My original intention was to allow writing a block1 option in control usage using the struct-based API, similar to coap_put_block1_ok(). It seemed an easy thing to do, and it was.

However, my larger goal is to complete the block implementation, which means addition of the client side for block1 and block2. I just started to look at this after I posted this PR. In this case, I think that the function coap_opt_add_block1() added in this PR instead will be used to write a message with the content, which uses a coap_block_slicer_t.

So, closing for now. My next step is to open an issue to describe the function names for the complete block implementation. Then I can revisit/rework this PR in that larger context.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/10702#issuecomment-451657300
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190105/39d87a3e/attachment.html>


More information about the notifications mailing list