You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 19, 2019. It is now read-only.
It would be nice to have some sort of "Fallback-ProtocolProcessor" to handle any HTTP calls that might have come from the user. From what I could see is this would perfectly fit into the WebSocketProtocolProcessor chain. All WebSocket protocol processors will fail on a normal HTTP call. In this case the "Fallback-ProtocolProcessor" could kick-in and handle the normal HTTP call by loading and returning some data.
Our plan is to add a simple REST API in parallel to the WebSocket connection which allows us querying some status information of the server (e.g. connected clients, data throughput etc.).
Sadly the protocol-processor chain is set-up hidden in the WebSocketServer.Setup method. I cannot see an easy way of adding a custom ProtocolProcessor to this chain.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be nice to have some sort of "Fallback-ProtocolProcessor" to handle any HTTP calls that might have come from the user. From what I could see is this would perfectly fit into the WebSocketProtocolProcessor chain. All WebSocket protocol processors will fail on a normal HTTP call. In this case the "Fallback-ProtocolProcessor" could kick-in and handle the normal HTTP call by loading and returning some data.
Our plan is to add a simple REST API in parallel to the WebSocket connection which allows us querying some status information of the server (e.g. connected clients, data throughput etc.).
Sadly the protocol-processor chain is set-up hidden in the WebSocketServer.Setup method. I cannot see an easy way of adding a custom ProtocolProcessor to this chain.
The text was updated successfully, but these errors were encountered: