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

implement message buffer #66

Open
emiltin opened this issue Aug 8, 2023 · 0 comments
Open

implement message buffer #66

emiltin opened this issue Aug 8, 2023 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@emiltin
Copy link
Collaborator

emiltin commented Aug 8, 2023

If a site tries to send messages during a disconnect, the messages must be buffered, and send when the connection is reestablished.

  • status subscriptions stay active during a disconnect, and still generate messages that are kept in the buffer
  • buffered status messages must have q=old
  • when connecting, the buffered messages are send as the last part
  • Command messages, Version messages, Watchdog messages and MessageAck are NOT buffered.

Spec states that a power outage must not cause the buffer to be lost. This would require that data is persisted on disk. I think we can wait with that part.

ref:
https://rsmp-nordic.github.io/rsmp_specifications/core/3.2/applicability/transport_of_data.html?highlight=buffer#communication-establishment-between-sites-and-supervision-system

https://rsmp-nordic.github.io/rsmp_specifications/core/3.2/applicability/transport_of_data.html?highlight=buffer#communication-disruption

@emiltin emiltin added the enhancement New feature or request label Aug 8, 2023
@emiltin emiltin added this to the 1.0 milestone Aug 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant