-
Notifications
You must be signed in to change notification settings - Fork 408
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
Add support to "/" for Read-Composite. #989
Comments
Together with @JaroslawLegierski we came up with an implementation for this case. Let me know what you think about this kind of solution. |
I'm not sure I get it 🤔 It looks like a kind of HACK at E.g for decoder : Map<LwM2mPath, LwM2mNode> decodeNodes(byte[] content,
ContentFormat format, List<LwM2mPath> paths, LwM2mModel model)
throws CodecException; when you call it with And so when you call it with But a |
Finally I was able to create a rough PoC, you can find it here. There's obviously a lot to improve in the code, but let me know if you even like my approach. |
I looked at this quickly and I feel it goes in the right direction. The main design issue is how we should handle (By the way I will be unavailable until 22th August) |
@sbernard31 do you think we could advance with this issue? |
I currently have hard time working on Transport Layer abstraction. 😅 But I can review PR or code and give some feedback is needed from time to time. Keep in mind that I will not integrate new feature in |
@sbernard31 Here is a proposal of displaying read-composite on root path. I’ve implemented it as a list, below is a link to changes. |
@sbernard31 I added integration tests for root case. Could you take a look on it? |
I looked at it quickly, I think this is the right direction. |
This is implemented by #1534 and will be available in next release 2.0.0-M14. |
Currently this is not supported :
(source : http://www.openmobilealliance.org/release/LightweightM2M/V1_1_1-20190617-A/HTML-Version/OMA-TS-LightweightM2M_Core-V1_1_1-20190617-A.html#Table-745-10-SenML-JSON-payload-in-the-request-to-all-objects)
The text was updated successfully, but these errors were encountered: