Expand websocket adapter, ensure connections/disconnections can be done dynamically, establish better pattern for dynamic subscriptions for use in other adapters #277
Labels
adapter: general
Issues and PRs related to input/output adapters in general
adapter: websocket
Issues and PRs related to our websocket adapter
type: enhancement
Issues and PRs related to improvements to existing features
Many adapters have static, wiring-time connection requirements, e.g. you need to provide a url or channel or topics at wiring time and cant make new connections dynamically. Starting with the websocket adapter where it is more (most?) relevant, we should establish a better pattern for dynamic subscriptions. This will be of particular importance in the upcoming redis adapter.
We may want to develop a common structure for subscriptions, though it will like have implementation-dependent details. As a simple example for websockets:
Then adapters will have the following structure:
For redis its even more complicated, but still the same overall pattern
The text was updated successfully, but these errors were encountered: