Skip to content
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

Optimization: copy of a packet is not stored by mesh protocol, but requested as necessary #8

Open
divanchykhin opened this issue Oct 8, 2015 · 0 comments

Comments

@divanchykhin
Copy link
Contributor

This optimization is applicable rather for terminal devices where GDP already keeps its copy of a packet. In general (up to particular calls) it's possible to ask GDP to provide that copy (unchanged), to supply it 9together with input parameters used last time) to SP, etc, and to get what otherwise we would have to store on MESH level.
Another variation of this optimization is to cause GDP to re-send the packet in a regular way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant