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
Despite it seeming like an attempt to create an Inception-like routing architecture for fun, I do have backend services primarily using WebSockets and would like to use wstunnel to expose them on a frontend proxy.
I have not reviewed the code, but I am just wondering if it is something that is easy to do with the current architecture. I guess it will be easier if request/response bodies are currently being chunked in the WebSocket tunnel, instead of fixing one request or response body to one message.
The text was updated successfully, but these errors were encountered:
Despite it seeming like an attempt to create an Inception-like routing architecture for fun, I do have backend services primarily using WebSockets and would like to use wstunnel to expose them on a frontend proxy.
I have not reviewed the code, but I am just wondering if it is something that is easy to do with the current architecture. I guess it will be easier if request/response bodies are currently being chunked in the WebSocket tunnel, instead of fixing one request or response body to one message.
The text was updated successfully, but these errors were encountered: