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.
Hi, this is an attempt at implementing a Simple Network Time Protocol (SNTP) over UDP sockets.
The client is pretty barebones: only unicast mode with a single server is supported, more advanced stuff like root delay and dispersion are skipped, and no adjustments are performed on the received timestamp.
Even so, I've tested it and it works pretty well, with an accuracy at least in the sub-second range. For timekeeping in embedded applications, which I plan to use it on, should be plenty good. However, let me know if more features need to be added to make it worth merging.
I've also taken the liberty to create an additional
apps
module for application-layer protocols, in case anyone decides to implement something else like TFTP or similar, to keep the crate more tidy. I'm not married to the idea though.