use MAX_TRANSMIT_WAIT from NetworkConfig as client awake time by default #716
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
msangoi
approved these changes
Jul 31, 2019
sbernard31
force-pushed
the
synchronized_max_transmist_wait
branch
from
22c8686 to
ea62317
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is PR is triggered by #712 (comment).
The LWM2M spec( v1.0.2 §8.3 Queue Mode Operation) does not really specify a time to wait at server time.
But it could make sense to use the default MAX_TRANSMIT_WAIT is
If this case using the value defined in NetworkConfig make sense too.