Alex Shnitman wrote:
> This actually got me interested so I downloaded the source code for
> Apache and looked. It indeed looks like it's parsing all the .htaccess
> files each time for each request. I wonder maybe it'd be easier to
> make a central cache of .htaccess files which would just be stat()'d
> on each request and re-parsed only if their dates have changed. Like
> mod_perl does for the perl files it loads (according to my
> understanding).
As I wrote in my response for Gaal, the "caching" is not the reason
for it, but the inability to guess in advance what htaccess should be
read.
> Anyone familiar with the Apache source here? Does it have some kind of
> a central shared memory area for sharing resources between all forked
> kids (which is where such a cache would have to reside), or how does
> it communicate with the kids anyway? Or does it at all?
Look at MM from Ralf Engelschall ( http://www.modssl.org ). But as I
wrote, this is not the solution for htaccess problem.
--
Eli Marmor
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
