feat: client discovery tag emission and capability learning for CEP-35#58
Open
harsh04044 wants to merge 1 commit intoContextVM:mainfrom
Open
feat: client discovery tag emission and capability learning for CEP-35#58harsh04044 wants to merge 1 commit intoContextVM:mainfrom
harsh04044 wants to merge 1 commit intoContextVM:mainfrom
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
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.
Part of #43
Implements the client side of CEP-35, the client now advertises its capabilities on the first outbound request and learns server capabilities from inbound discovery tags.
Changes:
Client emits discovery tags (support_encryption, support_encryption_ephemeral) on the first request only. Tags are
built from the client's encryption and gift wrap mode config. One-shot per session, subsequent requests carry no discovery tags.
Client event loop now calls learn_server_discovery() on every inbound event after decryption. The first event carrying discovery tags sets the session baseline (frozen after that). Capabilities are OR-assigned and never downgraded.
Public accessors: get_server_initialize_event() and discovered_server_capabilities().
7 unit tests and 3 integration tests covering tag emission conditions, one-shot behavior, OR-assign semantics, baseline freeze.