The current layout of the router and it's routes is not very flexible and was not made for the problems it currently tries to solve. Thus, it is going under refactoring to solve the drawbacks. In general, the following topics should be covered with the new router:
- Lightweight: Should be as fast or if possible even faster than the current implementation
- Design by contract: The router and it's routes get covered by interfaces
- The router should completly work with the request object instead of URL-strings
- Fixing bugs which are hard to fix without a BC-break
- The getInstance() method will be removed from all routes. Instead we will use a unified constructor
- getDefault() and getDefaults() will become interface methods
- The match() method will only allow an instance of Zend_Controller_Request_Http
The router will allow to not only give complete class names for the route types, but also just the actual route name (module, regex, chain, etc.). This allows for much less typing-work. The router will also accept arrays as configuration now instead of just Zend_Config instances (see unified constructors).
The currently known chaining will be dropped in favor of tree-matching. This will be setup similar to route chaining, but allow to match a segment in the tree only once, which will lead to better performance. For instance the router will only have to check for the hostname only once, instead of the current approach matching it for every single route again and again.
The hostname route will get an additional parameter, which will allow to enforce https connections. If activated, the route will only match when the connections comes via HTTPS, and assembling will prefix https:// instead of http://.
- Zend_Controller_Router_Rewrite_Route_Standard (or any other suggestions?)
Currently the router doesn't follow the coding standard completly, this will be solved together with the refactoring.