Manually maintaining a routes file is one possibility, however, if you'd like it to be a more automated process, I'd advise subclassing the Dispatcher.

If you were to do so, you could override key methods of the Dispatcher, such as getActionMethod, and include some localization code of your choice, which would simply translate the action name into whatever your application uses internally.

This would have to be done for controllers, as well as module names, if you 
were using those.

Joó Ádám wrote:
Read this: http://framework.zend.com/manual/en/zend.controller.router.html
I'd create an ini file to store the routes.


Regards,
Ádám

Reply via email to