Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wakama vs Awa #287

Closed
ekarlso opened this issue Aug 25, 2016 · 2 comments
Closed

Wakama vs Awa #287

ekarlso opened this issue Aug 25, 2016 · 2 comments
Labels

Comments

@ekarlso
Copy link

ekarlso commented Aug 25, 2016

What are the biggest differences between wakaama and Awa?

@serafimdasaudade
Copy link

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

These are for me the main reasons.

Cumps,

@torvall
Copy link

torvall commented Sep 11, 2016

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.

@GonZo GonZo closed this as completed Nov 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants