Hi Roberto,
yes "wakaama" doesn’t use "coaplib", it comes with it’s own coap implementation.
The tests/client is intended to demonstrate the usage of the lwm2m wakaama library. So for me it seems to be no good idea, to port a API demonstration client
to a other API :-).
I don’t know more docu for the client itself, except, that the objects are described in the LWM2M specification.
Mit freundlichen Grüßen / Best regards
Achim Kraus
Bosch Software Innovations GmbH
Communications (INST/ESY4)
Stuttgarter Straße 130
71332 Waiblingen
GERMANY
www.bosch-si.de
www.blog.bosch-si.com
achim.kraus@xxxxxxxxxxxx
Registered office: Berlin, Register court: Amtsgericht Charlottenburg, HRB 148411 B
Executives: Dr.-Ing. Rainer Kallenbach; Michael Hahn
Von: wakaama-dev-bounces@xxxxxxxxxxx [mailto:wakaama-dev-bounces@xxxxxxxxxxx]
Im Auftrag von Roberto P
Gesendet: Donnerstag, 7. Mai 2015 14:09
An: wakaama-dev@xxxxxxxxxxx
Betreff: [wakaama-dev] LwM2M client to RIOT
Hi,
as I wrote sometime ago I'm working on the porting of wakaama client in RIOT, as far as I got the CoAP library in RIOT is different from that one used in wakaama, should I adapt wakaama client to work with the RIOT CoAP library?
Why if I just port Wakaama in RIOT it doesn't work? Maybe I didn't port all the files?
PS. does it exist some documentation about the wakaama client? Just to make it easier to read among all that lines of code...