bapclenet at gmail.com
Thu Oct 29 15:32:17 CET 2015
>Also, you'd probably have to port it to RIOT first
Just to let you know, libcoap has already been ported to RIOT (as a
pkg as microcoap) 
Yes it does network registering automatically but I don't if this port
does it with the new network stack, need testing.
2015-10-29 15:19 GMT+01:00 Lennart Dührsen <lennart.duehrsen at fu-berlin.de>:
> Hi Ilias,
>> To use CoAP in my R21 boards should I rite the code of socket
>> programming (open a udp port ,etc) or just use the coap library and it
>> takes care about the socket?
> all the microcoap library does is create and parse payloads (CoAP
> packets), and it let's you register callback functions for each URI.
> You have to handle all the networking stuff, i.e. sending and receiving
> UDP packets, yourself.
> I'm currently working on the mostly absent documentation of microcoap,
> you can find it in this fork:
> It's not finished yet, but it might help you. For the networking stuff
> on RIOT OS, check out
> if you haven't already done so.
> The example code Baptiste pointed you to is indeed out of date, but the
> CoAP parts in it are still correct and should work, so you'd just have
> to change the socket calls etc.
> Regarding libcoap: It's a *lot* more code than microcoap, and yes, it
> does all the socket stuff for you. But its documentation, too, is pretty
> much nonexistent. Also, you'd probably have to port it to RIOT first, so
> I suggest you use microcoap for devices that will run RIOT OS.
> If you run into problems with microcoap, feel free to send me an e-mail.
> devel mailing list
> devel at riot-os.org
More information about the devel