Skip to content

sds: add optional support for ephemeral messages #2259

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

Closed
adklempner opened this issue Feb 11, 2025 · 0 comments · Fixed by #2302
Closed

sds: add optional support for ephemeral messages #2259

adklempner opened this issue Feb 11, 2025 · 0 comments · Fixed by #2302
Assignees

Comments

@adklempner
Copy link
Member

Per the specifications https://rfc.vac.dev/vac/raw/sds/#ephemeral-messages :

Participants MAY choose to send short-lived messages for which no synchronization or reliability is required. These messages are termed ephemeral.

Ephemeral messages SHOULD be sent with lamport_timestamp, causal_history, and bloom_filter unset. Ephemeral messages SHOULD NOT be added to the unacknowledged outgoing buffer after broadcast. Upon reception, ephemeral messages SHOULD be delivered immediately without buffering for causal dependencies or including in the local log.

To support this, the class for a message channel must accept a boolean flag for when ephemeral messages are enabled.

If ephemeral messages are enabled, then a check should be performed on all sent and received messages to determine if they are ephemeral. If so, skip buffering and local log as described above.

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

Successfully merging a pull request may close this issue.

1 participant