-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Remove support for multiple connection in a single server #3572
Comments
I’m working heavily with hapi for several years now, I can’t recall a single situation where we had depended on the multiple connections. On the other side, I do recall it being a bit confusing when starting to work with hapi. If you were to remove this feature, I think the onboarding would be much easer. Big +1 from me 💯 |
Would still be possible to spin up another server instance in the same process, no? |
@kpdecker yep. Just need to reuse the config. |
O agree 100% with @gr2m, I think the cognitive overload of multiple connections is not worth It. |
I’ve used this before and found it handy for the reasons outlined, but the workaround in #3572 (comment) would be more than acceptable. I too agree that the initial setup simplification alone is worth removing that feature. |
We use this feature all the time to redirect http requests on port 80 to use ssl |
I find it useful. I love that you can load plugins per connection. One use case is private routes for cache invalidation. |
I like the possibility to load plugins for specific connections, too. Is there any other way to restrict the effect of a plugin to certain routes or path-prefixes (e.g. a plugin should only affect |
@Mattii You just just losing the ability to select connections because there is always just one. The rest of the plugin options remain. |
This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions. |
hapi is (probably) the only framework that supports adding multiple ports to a single server instance. This was done for two use cases:
At this point, external tools would do as good a job at allowing you to manage multiple servers, each with a single port.
The text was updated successfully, but these errors were encountered: