Considering that this is the way CakePHP handles errors, yes, it is
certainly the most efficient option on its face. Others may dispute that.
I wouldn't really consider using Routes, because the routes are determined
*before* the existence of any Controllers or Actions is confirmed. I do,
however, have a catchall clause in my routes.php file that says:
Router::connect('/*', array('controller' => 'pages', 'action' =>
'display'));
This is basically in a situation where every other route is specified by
the routes.php file. The reason for this is simply because so much of what
my company wants to do in terms of routing has little to nothing to do with
the way CakePHP wants to do things. If this helps you, go for it.
--
Our newest site for the community: CakePHP Video Tutorials
http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others
with their CakePHP related questions.
To unsubscribe from this group, send email to
[email protected] For more options, visit this group at
http://groups.google.com/group/cake-php
