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.

Sign up for GitHub

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

Jump to bottom

Add API to choose default content type as client side #574

Closed
sbernard31 opened this issue Sep 27, 2018 · 1 comment
Closed

Add API to choose default content type as client side #574

sbernard31 opened this issue Sep 27, 2018 · 1 comment
Labels
client Impact LWM2M client new feature New feature from LWM2M specification

Comments

@sbernard31
Copy link
Contributor

Currently, the leshan client use TLV as default content type.
If the accept option is present in the request it will try to decode using this one.

It could be great to add a per resource or at least per object default content type API.
@sbernard31 sbernard31 added new feature New feature from LWM2M specification client Impact LWM2M client labels Sep 27, 2018
sbernard31 added a commit that referenced this issue Nov 12, 2018
@sbernard31
#574: Add API to choose default content type as client side
56979c7
sbernard31 added a commit that referenced this issue Nov 12, 2018
@sbernard31
#574: Add API to choose default content type as client side
cd35be7
@sbernard31 sbernard31 mentioned this issue Nov 12, 2018
Closed
sbernard31 added a commit that referenced this issue Dec 3, 2018
@sbernard31
#574: Add API to choose default content type as client side
3a565f8
@sbernard31
Copy link
Contributor Author

Implemented by #615 which is now integrated in master.

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

No branches or pull requests
1 participant
@sbernard31