Hi Roberto,
The tests/client has a lot of features for testing that are not necessary for a production client. You can use it as-is but I would suggest to strip it for all
the unneeded code (like battery level changes, command-line UI, Objects save/restore). Somehow a wakaama client can be just a main function will initialization phase and a loop. The “real work” is done by the object plugins.
Porting wakaama without adapting to libcoap is possible and it will definitively work.
Regards,
David Navarro
From: wakaama-dev-bounces@xxxxxxxxxxx [mailto:wakaama-dev-bounces@xxxxxxxxxxx]
On Behalf Of Roberto P
Sent: Wednesday, 13 May, 2015 09:35
To: wakaama-dev@xxxxxxxxxxx
Subject: Re: [wakaama-dev] wakaama-dev Digest, Vol 10, Issue 11
The tests/client is intended to demonstrate the usage of the lwm2m wakaama library.
So what would you suggest to do, in your opinion should I write my own client? I guess that would took a lot of time, and I have just 1-2 months, furthermore it's for a thesis, so I just need to make a working client able to do the basic
stuff, isn't okay the tests/client in wakaama to do that?
So for me it seems to be no good idea, to port a API demonstration client to a other API :-)
What about just porting wakaama without adapting it to the libcoap? Since that it's has its own CoAP implementation, should it work, or not?
---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number: 302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
|