Gaal Yahas wrote:
>
> On Thu, Jan 06, 2000 at 10:40:31PM +0200, Eli Marmor wrote:
>
> > running CGI-BINs, the parsing (of scripts like Perl and PHP), the
>
> (You've got FastCGI, mod_perl and commercial solutions for that)
I deeply thank you for trying to teach me Apache. I really appreciate
it!
The guy asked if something has overhead and if this is a reason to
avoid it, and I only tried to answer him that (1) it DOES have this
overhead and that (2) it is not a reason to avoid it because there
are zillion of other things which their overhead is much worse and
that if he avoids this "thing" (shared modules) he pays a lot in terms
of mainatainability.
> > need to load and parse htaccess files (sometimes even per request),
>
> I'm no expert in web servers, but this looks strange to me. Could
> you explain why there isn't some way for a user to signal the server
> that he had changed his .htaccess file?
This is not the only problem. The main problem is the inability to
guess what directories to read. Sometimes, there are 10 levels of
directories under htdocs and 20 sub-directories per each directory;
Should we read 20^10 directories, just because somebody may want to
access them later? And what if there are hundreds of users with home
directories (or sub-directories, more exactly) which are accessible by
the web server?
> If this is really such a
> bottleneck, we can (it seems to me) change the semantics a bit and
> put the responsibility on the users' side.
It is already done. All the Apache books recommend the users to avoid
htaccess, for better performance, unless there is no other way (for
example, in virtual web hosting, it's usually impossible to let
anybody access the main httpd.conf).
> (In case I haven't made myself clear, I mean something like asking
> users to kill -1 the server after every time they modify their
> htaccess. I realize they can't do that themselves, but surely there
> is some sort of mechanism to deploy here that's cheaper than
> what you describe above.)
Apache already supports the "kill -HUP" for re-reading the
configuration files, but as I already wrote, it can't solve the
problem of htaccess.
--
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]
