Wow, there seems to be quite a bit of confusion going around about the whole routes vs. htaccess thing lately. First, read this: http://groups.google.com/group/cake-php/msg/2cdc97025c590dda
Wait, stop. You haven't read it yet, have you? Okay that's better, now continue: As far as performance goes, a little str_replace is probably the lowest-overhead operation in the whole process. In fact, mod_rewrite is comparatively high-overhead. One thing you can do to mitigate this is move the rewrite rules in Cake's .htaccess files into <virtualhost /> and <directory /> tags in your Apache conf. Rewrite rules create an internal redirect within Apache, which is part of why it is such an expensive operation, though still "silent" (i.e. transparent to the client browser). Again, routes aren't for redirecting, they just point Cake at the controller action to execute. For most apps, you'll never even need to mess with the routes config, as it is setup by default to work according to Cake's conventions. Lastly, with the tricks presented here on the mailing list, it is very easy to tweak URL's for optimal SEO, using both routes and text replacement. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~----------~----~----~----~------~----~------~--~---
