On Thu, Jul 30, 2009 at 1:35 AM, JamesF<[email protected]> wrote: > > i would be interested in seeing the gains for this too. only problem > is you need access to http.conf which might destroy the portability of > your app if you plan to distribute it. still if you are talking about > a server the serves 20000 visitors a day maybe the gains are worth it. > i actually might try this myself for fun.
Sure, it's not for everyone. But I wouldn't go so far as to say it would "destroy the portability" of a site. It's just an .htaccess file, after all. And I doubt too many people wantonly change their server setup with the expectation that everything will work without any thought put into it. (oh, wait ...) Anyway, with AllowOverride being on and even a single .htaccess file present somewhere in the path of a request (many websites that use them have them at root) the server then has to check every other directory in that path. Plus, it has to parse the htaccess file. That's for every request. Putting the same instructions in httpd.conf will certainly shave *some* request time. That being said, the main requests with a Cake app go only as deep as webroot/index.php (although there's alo all the css/js stuff). I agree that it'd be interesting to run some tests (with ab or something similar) against a Cake app both with and without .htaccess files. A little weekend project, perhaps. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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?hl=en -~----------~----~----~----~------~----~------~--~---
