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

allow for more than one custom option #5

Open
monteslu opened this issue Sep 22, 2014 · 4 comments
Open

allow for more than one custom option #5

monteslu opened this issue Sep 22, 2014 · 4 comments

Comments

@monteslu
Copy link

it's currently labeled "Custom Options", but you can only add a single option.

@mkovatsc
Copy link
Owner

Yes, I started with this feature, but it was mainly for test purposes. So far, I could not see the benefit of investing time for this. Do you have a use case?

@monteslu
Copy link
Author

We're using 2 custom attributes for user/pass authentication. Doesn't necessarily have to be dynamic, but just a couple more custom fields would be fine.

@petrovcicklemen
Copy link

petrovcicklemen commented May 2, 2016

The OneM2M standard specifies, in its specification for the COAP protocol, multiple custom options, which should/could be carried in a COAP message. Although it isn't that hard to manually build a message using the Californium library, it would certainly speed things up for future users.

@DariusMR
Copy link

Hello
Yes we need more than one custom option. It could be very useful for OneM2M or other standards
I hope this project is still active :)
Have a nice day !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants