There's no need to be instantiating 100's of routes for a single request.
What you should do, is use a custom route class to bind the request to a controller/action.
http://mark-story.com/posts/view/using-custom-route-classes-in-cakephp
On Jul 2, 2011, at 9:03 AM, mece7@yahoo.com wrote:
> custom routes slow down my application
>
> I have loop in the routes in which I'm connecting and processing more
> than 100 custom routes but now my app is experiencing hard time when
> is loading
> Render Controller Action 6600 ms
>
> Any suggestion how to resolve this
>
> --
> 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
> cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
--
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
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
No comments:
Post a Comment