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.

Sign up for GitHub

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

Jump to bottom

Clarify idempotency requirements #9

Open
jimmarino opened this issue Oct 1, 2024 · 0 comments
Open

Clarify idempotency requirements #9

jimmarino opened this issue Oct 1, 2024 · 0 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@jimmarino
Copy link
Contributor

Idempotent behavior and de-duplication are required for reliable message handling. The specification needs to clarify how this behavior is treated as an optional quality of service:

  1. A connector should not be normatively required to implement reliable messaging
  2. If a connector does implement reliable messaging, it must perform de-duplication based on the message id.
@jimmarino jimmarino added documentation Improvements or additions to documentation enhancement New feature or request labels Oct 1, 2024
@juliapampus juliapampus transferred this issue from eclipse-dataspace-protocol-base/DataspaceProtocol Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jimmarino