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

Transactional API at client side #968

Open
sbernard31 opened this issue Jan 29, 2021 · 4 comments
Open

Transactional API at client side #968

sbernard31 opened this issue Jan 29, 2021 · 4 comments
Labels
client Impact LWM2M client new feature New feature from LWM2M specification

Comments

@sbernard31
Copy link
Contributor

sbernard31 commented Jan 29, 2021

Bootstap operation and write composite(#959) need atomic modification of the LWM2M tree.
So maybe we need a commit/rollback mechanism or at least an API which allow user to implement it.

@sbernard31 sbernard31 added new feature New feature from LWM2M specification client Impact LWM2M client labels Jan 29, 2021
@sbernard31
Copy link
Contributor Author

@moznion, do you already feel you need something like this ?

@moznion
Copy link
Contributor

moznion commented Feb 4, 2021

Yes, absolutely! Sometimes I was feeling I wish I were able to manipulate the tree atomically.

@sbernard31
Copy link
Contributor Author

Do you already have a vague idea about what the API should looks like ?

@sbernard31
Copy link
Contributor Author

sbernard31 commented Jul 6, 2021

This could maybe also used to support a more robust bootstrap session at client side. (see OpenMobileAlliance/OMA_LwM2M_for_Developers#523)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client Impact LWM2M client new feature New feature from LWM2M specification
Projects
None yet
Development

No branches or pull requests

2 participants