On 12 May 2010 17:17, Kevin Kinsey <kdk@xxxxxxxxxx> wrote: > > Well, again, I'm not purporting to be an authority, but the > first thing that comes to mind is that my reasoning would be > much the same as my reasoning in building stuff: I've got a nice > STIHL chainsaw, but I don't need it to cut two-by-fours, and > I've got access to a Hole Hawg but don't need it to make a > path for a CAT5 cable. I guess you could call the concept > "avoiding overkill", but I'm not cognizant enough with the > inner workings of Apache to know really how much of a "hit" > the rewrite module makes. I suppose, in terms of computing, it's > kind of similar to a Unix philosophy: small tools that > do one job without extra fluff. > Doing it in PHP is like to be "doing it with extra fluff". Mod_rewrite is designed for rewriting and it does it well. Doing the same job in PHP is likely to use more resources and be more complex. In short: using mod_rewrite for url rewriting is not "overkill" - it's using the proper tool for the job. Regards Peter -- <hype> WWW: http://plphp.dk / http://plind.dk LinkedIn: http://www.linkedin.com/in/plind Flickr: http://www.flickr.com/photos/fake51 BeWelcome: Fake51 Couchsurfing: Fake51 </hype> -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
