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
{{ message }}
This repository has been archived by the owner on Dec 12, 2023. It is now read-only.
I think Tornado would be a good choice for a internal REST API provider (as it supports many cool and useful features like user authentication). aiohttp would also be a candidate, however, there are some features missing.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In order to enable applications to interact with LwM2M clients connected to myLwM2M server, a REST API would be helpful.
The following proposal describes possible REST resources:
GET /clients
- get clients (paginated - to avoid too many results, query params possible for filtering)GET /client/{id}
- query a client data by an endpoint idPOST /client/{id}/read/{object_id}/{instance_id}/{resource_id}
- read on object ID,instance,resource, the last two are optionalPOST /client/{id}/write/{object_id}/{instance_id}/{resource_id}
- write on given object/instance/resource, payload must contain the new valuePOST/client/{id}/writeattributes/{object_id}/{instance_id}/{resource_id}
- write attributes/configure observe. Payload contains the attributes.POST /client/{id}/execute/{object_id}/{instance_id}/{resource_id}
- execute an operation on object/instance/resource....
And so on.
As a content type i would suggest
application/json
.The text was updated successfully, but these errors were encountered: