We would like the WebSocket protocol supported in plaintext.
This is very similar to #61 but instead of HTTP it is HTTP(S) with protocol upgrade to WebSockets immediately.
Likewise, would be cool if this was netty.
Same requirements for basic functionality.
Describe the solution
Netty handler for WebSockets, conforming to existing API interfaces.
Alternative methods
It is possible to lift the existing implementation. Please try to avoid this as I would like to re-think how the protocol processing works.
Key requirements for protocol
handling of messages is independent of whether sync or async
handling of messages is clear and obvious (what is input, what is output, how can it fail)
It should be testable at all levels of units. We should be able to verify the lifecycle of the protocol works without having to perform complex SurrealQL against a live instance. We should be able to fake responses from the server.
SurrealDB version
SurrealDB beta-9; java driver commit 50aa1d6
Contact Details
hugh@surrealdb.com
Is there an existing issue for this?
[X] I have searched the existing issues
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Is your feature request related to a problem?
We would like the WebSocket protocol supported in plaintext. This is very similar to #61 but instead of HTTP it is HTTP(S) with protocol upgrade to WebSockets immediately.
Likewise, would be cool if this was netty.
Same requirements for basic functionality.
Describe the solution
Netty handler for WebSockets, conforming to existing API interfaces.
Alternative methods
It is possible to lift the existing implementation. Please try to avoid this as I would like to re-think how the protocol processing works.
Key requirements for protocol
SurrealDB version
SurrealDB beta-9; java driver commit 50aa1d6
Contact Details
hugh@surrealdb.com
Is there an existing issue for this?
Code of Conduct