5 ms·
there are so many php routers these days that any "fast" claims should probably be accompanied by benchmarks. routing is a fairly uncomplicated task and the sp
by leeoniya 12y ago
there are so many php routers these days that any "fast" claims should probably be accompanied by benchmarks.
routing is a fairly uncomplicated task and the speed difference will only become apparent at really high loads.
http://c9s.github.io/Pux/ http://c9s.github.io/Pux/
http://auraphp.com/packages/Aura.Router/ http://auraphp.com/packages/Aura.Router/
http://zaphpa.org/ http://zaphpa.org/
http://toroweb.org/ http://toroweb.org/
https://github.com/dannyvankooten/PHP-Router https://github.com/dannyvankooten/PHP-Router
https://github.com/symfony/Routing https://github.com/symfony/Routing
http://docs.phalconphp.com/en/latest/api/Phalcon_Mvc_Router.html http://docs.phalconphp.com/en/latest/api/Phalcon_Mvc_Router....
- nubs 12y agoThis list is missing https://github.com/nikic/FastRoute https://github.com/nikic/FastRoute which is definitely worth looking at.
- ams6110 12y agoI used Epiphany last time I needed something like this. https://github.com/jmathai/epiphany https://github.com/jmathai/epiphany Note that is more than a router, it's a microframework.
- krapp 12y agoWhat would you want a 'minimally viable' microframework to include, in terms of functionality? This has come up a couple of times in PHP framework and router threads, and i've been wondering what it would look like (it would probably be even smaller than Slim Framework). I've gotten as far as including Composer and a rather barebones router and telling people to just include whatever else they want but I suspect other people would want more. I find it annoying when frameworks include dependencies I don't want, particularly an ORM or a templating engine, but I understand for a lot of people, that's the point (not having to pick dependencies themselves.)
- Nickoladze 12y agoDont forget µ which is totally a legit router https://github.com/lastguest/mu https://github.com/lastguest/mu
- insky 12y agoWhich begs the question, how on earth do you choose one? Edit: as in, which router do you pick and how do you pick one? Choice can lead to decision paralysis.
- apsdehal 12y agoCheck whats your need, if you are building up much bigger apps go for a fully fledged framework, rest for small apps you can use microrouters , according to your need, each has its own unique features.
- icedchai 12y agoFor small apps, you don't need a "router", period. Routing is done by the file system and placing .php files in directories!
- krapp 12y agoOne of the benefits of using a url router is access control - you could have a problem with just letting every file be executable by url, especially if you happen to have a remote file inclusion issue anywhere. With a router you know explicitly what can get invoked and what can't. Although, doing it without a router is probably always going to be faster.
- insky 12y agoA late trick I discovered, was that you can configure your php instance to inclued a file with every script. For example the following can be added to .htaccess: php_value auto_prepend_file 'before.php' You can then use that for bootstrapping, front controller and to limit access. Can be a bit clumsy, but it's nicely divorced from simple page controllers.
- kawsper 12y agoI liked Klein.php as well. https://github.com/chriso/klein.php https://github.com/chriso/klein.php
- chime 12y agoI love http://flightphp.com/ http://flightphp.com/