Simplify NXS to registration, heartbeat and outcomes - #13
Merged
Conversation
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.
NXS now has three integration flows: registration, heartbeat, and stateless admission with asynchronous outcomes. Replace the experimental 17-operation surface in place with seven operations; completion starts the process generation, heartbeat exchanges profiles, admission keys and applied lifecycle state, and
outcomescarries transport and game feedback. No new API version or compatibility adapter.The guide starts with those three flows and links to a separate wire reference and updated schema. The client persists one-time keys, preserves original replayed leases and retirement deadlines, and backs off outcome failures independently of heartbeat renewal. Native admission remains local with no per-join provider operation.
Validation: canonical signing/encryption fixtures; Java provider contract and journey tests; real native admission tests for first-packet handling, capacity, replay and DTLS fingerprint binding; local Warden/native end-to-end bench. These prove native transport, not stock-client gameplay.