On 03/09/2010 01:05 AM, Philip Wigg wrote:
> On 8 March 2010 18:56, Jonathan Zuckerman <j.zuckerman@(protected):
>  
>> Hey Rich, and anybody else who knows about this, what you've just said
>> touches on a question I've been wondering about: a few folks at work have
>> always told me that .htaccess was a really slow way to load configuration
>> because it needs to be checked per directory, as opposed to the global
>> configuration in httpd.conf or whatever that can be cached for the whole
>> webserver.
>> How true is this really? I've worked on a couple of high-load
>> high-availability webservers and we've never made a point of putting general
>> site configuration and rewrite rules in the httpd.conf file, using .htaccess
>> in the site root instead..
>> Having the ability to modify .htaccess without needing to restart the
>> web-servers is nice but certainly not essential, we generally restart the
>> webservers anyway when we make changes to the site in order to clear the
>> op-code cache. I'm wondering though if we could retire a server and still
>> support the same load, or at least see performance increases with a little
>> jiggering of the configuration..
>> I guess the way to test this would be to just do it and see the results,
>> I'll let you know what I find out, but hearing about actual experiences from
>> anybody else would be nice too.
>>  
> There's a useful section in the documentation about this subject:-
>
> http://httpd.apache.org/docs/2.2/howto/htaccess.html#when
>
> -- Phil
>
>  

Thank to all of you for your help and links. I'll definitely give an
in-depth look into those.

wish you all a nice time.

--
জয়দীপ বক্সী


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@(protected)
 "  from the digest: users-digest-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)