Routing is not just some pattern matching. What is different from using different files to handle routing and a centralized router/dispatcher is:
- centralized bootstrapping - code duplication removal - being able to plug custom logic per URI (not just physical paths, may be logical paths computed through a map, for example) In general, where you'd have the filesystem as a "map" of your application logic, you now have the equivalent `function route($url);`, which is more powerful given that you can plug any logic into that step. Marco Pivetta http://twitter.com/Ocramius http://ocramius.github.com/ On 29 January 2014 04:28, dennyamd <[email protected]> wrote: > Aside from SEO and perhaps URLs looking pretty, are there any arguments for > using Routes? > > I am talking about: > * localhost/path/file.php?item1=value1&item2=value2 vs > * localhost/controller/value1/value2 > > I apparently missed that transition period of the Internet. > > > > -- > View this message in context: > http://zend-framework-community.634137.n4.nabble.com/Why-ZF2-uses-Routes-tp4661553.html > Sent from the Zend Framework mailing list archive at Nabble.com. > > -- > List: [email protected] > Info: http://framework.zend.com/archives > Unsubscribe: [email protected] > > >
