feat: transport abstraction + optional redis support (wip)#68
Merged
Conversation
…ls anymore. this helps to add more backends like redis
Closed
Allows velocity and backend runtimes to bootstrap the correct endpoint on startup while preserving reconnect behavior and cleaner enum config validation errors.
…into redis-support
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.
This PR introduces a transport abstraction layer and prepares CommandBridge for optional Redis support
The goal is to decouple the core logic from WebSocketChannel and make the transport interchangeable. WebSocket remains the default and should behave exactly like before. Redis will be added as an optional transport mode, not enabled by default.
Main changes so far:
Endpointinterface to replace directWebSocketChannelusageSendOperationto be transport-agnosticSessionHubto be keyed byclientIdinstead of channelWsEndpointimplementationWsServerto use endpoint abstraction while keeping existing behaviorNo functional behavior change is intended for WebSocket mode.
Next steps: