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

Clarify that every message should have a unique GUID. #134

Merged
merged 3 commits into from
Jan 19, 2024
Merged

Conversation

otterdahl
Copy link
Contributor

  • Clarify that every message should have a unique GUID.
  • Move some content from table in order to make it easier to read in the online view

@marcgarba
Copy link

Nice clarification and reorganization.
a little typo: "mId is used i all messages as a reference for the message ack" => "in".

@otterdahl
Copy link
Contributor Author

otterdahl commented Nov 10, 2023 via email

@otterdahl otterdahl mentioned this pull request Nov 15, 2023
14 tasks
@emiltin
Copy link
Contributor

emiltin commented Nov 16, 2023

Let's be even more clear and state that even if you resend the same messages again, it should have a new GUID.

@emiltin emiltin added this to the 3.2.2 milestone Nov 16, 2023
@otterdahl
Copy link
Contributor Author

Let's be even more clear and state that even if you resend the same messages again, it should have a new GUID.

The PR has been updated. Merging this

@otterdahl otterdahl merged commit 2420344 into 3.2.2 Jan 19, 2024
@otterdahl otterdahl deleted the resend_guid branch January 30, 2024 08:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants