Thank you for submitting this pull request! We appreciate you spending the time to work on these changes.
What is the motivation?
To allow the use of the same WS connection for multiple queries at the same time (thread safety) and multiplexing of incoming live query results from multiple streams.
[ ] 🔧 Bug fix (non-breaking change which fixes an issue)
[x] 🥂 Improvement (non-breaking change which improves an existing feature)
[x] 🚀 New feature (non-breaking change which adds functionality)
[x] 💥 Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🔐 Security fix
What does this change do?
Provides for use of a connection manager to route incoming requests from the web socket, and handles ensuring every request is replied to with the actual response rather than just the first one to come in.
Thank you for submitting this pull request! We appreciate you spending the time to work on these changes.
What is the motivation?
To allow the use of the same WS connection for multiple queries at the same time (thread safety) and multiplexing of incoming live query results from multiple streams.
Type of Change
What does this change do?
Provides for use of a connection manager to route incoming requests from the web socket, and handles ensuring every request is replied to with the actual response rather than just the first one to come in.
This is additional implementation on top of #78
Is this related to any issues?
34 #78
Have you read the Contributing Guidelines?