-
Notifications
You must be signed in to change notification settings - Fork 402
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
Incorrect link objects are implicitly sent on update #8
Comments
You're right, since the refactoring/API changing all about object links (register, update, discover) is in a pretty bad state. |
So, I fixed the problem of link object which does not contains instance ID at registration. client.send(new UpdateRequest(
"registrationId", null, null, null,
LinkFormatHelper.getClientDescription(client.getObjectEnablers(), null))); not really sexy ! |
Yes, may be we can improve this in the future... |
The implementation of the visit method with UpdateRequest still contains this implementation:
I think it should be implemented as described above
|
It was a bug. it should be fixed now. |
…-session Store PSK Identity in the DTLS Session
It seems that on performing an update request from client (with empty (null) object links argument)
CoapClientRequestBuilder
performs an implicit paylodizing of link objects from the object definition invisit(UpdateRequest)
:Because the object links are not required for update, this conversion should only be performed if link objects are provided with the UpdateRequest, like this:
BTW the link objects found in definition are also containing only object IDs, like
</1>,</3>
etc. This seems to be an incorrect behavior invisit(RegisterRequest)
.The text was updated successfully, but these errors were encountered: