-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Realtime Connections Support #17
Comments
So there is definitely a plan to implement WebSockets support into the Go proxy on the roadmap, my main concern however is usage of server resources especially on our official server. I may just add an optional flag or setting that can be supplied to the server to toggle the capability. Just referring to the other issue, could you clarify what you meant by "still trying to adopt the original version of http proxy server so we could use a single proxy for both types of requests"? |
sorry for the late response |
Ah, no worries! |
See also hoppscotch/hoppscotch:#3062. Especially with the push for Hoppscotch as an enterprise product and for self-hosting purposes I think it would be useful to add this functionality to the proxy even if it is not used by hoppscotch officially due to the aforementioned concerns about resource consumption. I will look to implement this in the proxy server behind a |
related: hoppscotch/hoppscotch#175
The text was updated successfully, but these errors were encountered: