feat(ipc): add memoized pattern subscriptions - #19
Merged
Merged
Conversation
Add explicit prefix subscription APIs and v2 frames while preserving exact-name semantics. Cache deduplicated routes with atomic mutation invalidation, bounded selectors, and per-connection lifecycle handling. Prepare the compatible 9.3.0 workspace release.
This branch was successfully deployed
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.
IPC clients can now subscribe to families of registered broadcast names, such as
Order*, without listing each type. The new pattern APIs preserve literal exact subscriptions and deliver once per connection when selectors overlap.Routing memoizes deduplicated recipient sets in a bounded cache. Subscription mutations invalidate the cache under the same state lock used by forwarding, including unsubscribe, disconnect, and connection replacement. Pattern requests validate atomically and respect the existing request rate limiter. Pattern-only clients use subscriber idle timeouts.
This prepares workspace release 9.3.0 with additive request/response types and v2 frame tags. Older servers close connections receiving the new tags, so clients must upgrade their server before using pattern methods. Documentation covers syntax, limits, unsubscribe behavior, and best-effort delivery.
Validation: