Re: [Mod-c-users] Fwd: some stuff

[Matej U. <mat...@gm...>]

On Thu, 2006-08-24 at 12:55 -0300, Gonzalo Arana wrote:
> I've changed my mind on this a little bit.  I've wrote this:
> 
> 1) EHTMLAllowOnDemand on|off: if set to off, every ehtml must be LoadEHTML'ed.
> 2) EHTMLCacheAutoRefresh on|off: if set to on, cached ehtml entries
> will be autorefreshed if file has changed (mtime & size are checked).
> 
> How does this sound to you?

Oh, the AutoRefresh stuff... Yeah... Well, this will be a more tricky
thing. You see, HTTPD creates child processes to handle web pages in a
secure manner (perhaps there are other reasons to it, but it's not
important). So, every request is processed in those child processes. The
catch is that whenever we Refresh an EHTML library, it would happen only
in that particular child process that received the request (other child
processes' caches would not be refreshed).

After a selected amount of precessed requests HTTPD simply kills those
child processes and recreates them instantly afterwards (to prevent
memory corruption etc...) - this is also configured in the httpd.conf
file (I have it configured that HTTPD respawns child processes after
every 20.000 requests).

Anyways, those newly recreated processes would again have the cache as
was created at httpd's startup time! You see, whatever
refreshing/caching there happened at run-time would be nulled when
respawning of processes happens.

This does not mean that it doesn't make sense to refresh/cache
libraries. I just wanted to tell you what happens in httpd.

Well, at least I think this is what happens in httpd :-D I could be
wrong :-P


Enjoy