You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I used Wakama on a project for a few months. But I moved to AwaLWM2M due to the following reasons.
1 - I think the documentation is better.
2 - The code is easier to read,
3 - It can be compiled into an environment easily contiki.
4 - There are many examples
Wakaama is (sort of) a LWM2M library that you add to your server and client (and optionally bootstrap server) projects and only provides basic functionality. You have to deal with socket handling, process control, etc. yourself.
AWA, on the other hand, is a set of client, server and bootstrap daemons that take care of all networking and process control out of the box and provide an IPC API with which your client and server applications interface with to do LWM2M operations.
AWA also provides a small footprint client targeted at constrained devices that can be access through a static API.
What are the biggest differences between wakaama and Awa?
The text was updated successfully, but these errors were encountered: