-
Notifications
You must be signed in to change notification settings - Fork 407
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
Including timestamped send option to SendService #1584
Comments
Iam not sure but maybe Do you test the it ? it is able to collect timestamped data then send all collected data ? You can test its behavior with leshan-client-demo ? using this interactive command
You could have code example here : Lines 337 to 357 in f23254c
and Lines 307 to 335 in f23254c
If this doesn't match you need, could you try to explain why ? 🙏 |
Does that work for you ? should we close this issue ? |
Yes, this actually looks to be exactly what we needed, thank you! I will close the issue. |
Question
Currently the default
LeshanClient
creates an implementation ofSendService
that can be used to send data from the client to the server. This implementation contains both the sync and async versions of the send. However,DataSenderManager
used to send the data also supports the versions of sendData that takeTimestampedNodes
instead of plain LwM2mNodes:vs.
Would it make sense to include this timestamped option to the default client / SendService interface? Or would this be unnecessary bloat for most users? Currently, if the timestamps are needed, a custom client class, or at least a clientBuilder class, is needed.
Changes would be needed to
SendService
interface and theLeshanClient
for this. Implementation itself is trivial, e.g.Depending of course if we want the timestamp to be passed or automatically created.
This case comes up when we use the LWM2M send service to push event related measurements from the client. I'm not sure if it's a common use case or not.
If this sounds good, I could submit a PR for this.
The text was updated successfully, but these errors were encountered: