Repository navigation
[#553] Always include a bdSeq number for scoping messages to a session - #619
Merged
wes-johnson merged 1 commit intoAug 10, 2026
Merged
Conversation
…sages to a session Require bd_seq in every message an Edge Node publishes, so any single message can be attributed to the session that produced it. Adds *-bdseq statements for NDATA, NRESP, DBIRTH, DREBIRTH, DDATA, DRESP, and DDEATH. Corrects two blocking defects: - payloads-bd-sequence-num-included named only NBIRTH/NREBIRTH/NDEATH and did not cover the NMETA/NMMETA/DMETA/DMMETA that Ch4 already required. - payloads-bd-sequence-num-incrementing described seq behavior (increment per message), contradicting topics-nbirth-bdseq-increment and operational-behavior-rebirth-action-3. Now increments per MQTT CONNECT. Adds payloads-bd-sequence-num-session-constant for the session invariant, renames the mislabelled _seq_ payload field description to _bd_seq_, and adds host-partial-bdseq-scope and host-partial-bdseq-new-session so a partial-subscription Host Application can scope a message to a session without having observed the BIRTH sequence that opened it. Also normalizes 696 non-breaking spaces used as indentation in Ch6 example payloads; all 15 example payloads now parse as valid JSON.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Require bd_seq in every message an Edge Node publishes, so any single message can be attributed to the session that produced it. Adds *-bdseq statements for NDATA, NRESP, DBIRTH, DREBIRTH, DDATA, DRESP, and DDEATH.
Corrects two blocking defects:
Adds payloads-bd-sequence-num-session-constant for the session invariant, renames the mislabelled seq payload field description to bd_seq, and adds host-partial-bdseq-scope and host-partial-bdseq-new-session so a partial-subscription Host Application can scope a message to a session without having observed the BIRTH sequence that opened it.
Also normalizes 696 non-breaking spaces used as indentation in Ch6 example payloads; all 15 example payloads now parse as valid JSON.