-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Consider symfony/routing 4.1? #5
Comments
I'm a little confused about "faster". As far as I read, there are vast differences between first route, last route, failed match, dynamic case, static case, mixing dynamic&static etc. Perhaps the chunking sizes got outdated with performance improvements related to PCRE 2, PCRE JIT or such. I think if that's the case, it should be trivial to change that upstream instead. Regarding the features - not sure whether we really need that here - you can trivially clone the router and attach two different routes to either of them and attach it to your vhost dispatcher. |
About faster, the second part explains why we now achieve better performance: https://medium.com/@nicolas.grekas/making-symfony-router-lightning-fast-2-2-19281dcd245b |
@bwoebi We no longer have vhosts. ;-P @nicolas-grekas I've considered that, but went with what we already had in the few years of Aerys lifetime. Seems like it requires 7.1, while currently all our projects require 7.0. |
@kelunik I have lost a bit the orientation with all the packages - before it was rather nicely in one place. To my knowledge consensus was to split vhosts as a middleware into a separate package? |
It should be very simple to build another package like this based on |
It inherits from FastRoute, now faster and with more features.
See https://medium.com/@nicolas.grekas/making-symfonys-router-77-7x-faster-1-2-958e3754f0e1
The text was updated successfully, but these errors were encountered: