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
Give feedback to end user when something wrong occurs on notification reception. #206
Comments
If you want a short term solution, you can implement your own DefaultLwM2mNodeDecoder. |
Just for anyone that wants a Custom decoder that is tested and works with Bosch XDK's observe: https://gist.github.com/hytromo/b9c5ec7a308e24ca7cec3afcb86642e2 (implements the text decoder if the format is null) Use it like this:
|
I renamed this issue because the conclusion of the #204 discussion was to "handle response of observation like other response (catch+log+return it to application layer)" |
Even though the specs requires the client MUST send content format in the response, the server could have better handling strategy if this happens.
Please refer to the discussion in the pull request: #204
One possible solution is to add Not spec compatible related APIs:
public class NotSpecCompatibleAPIs{
static void setResponseContentFormatIfNull(CaliforniumObservationRegistryImpl reg, ContentFormat cf){
}
}
I choose CaliforniumObservationRegistryImpl as the parameter because it will not change the public ObservationRegistry interface.
It is not elegant, but it helps to developers easy because it takes time to ask device manufacturers to fix their code.
The text was updated successfully, but these errors were encountered: