>
> apache just doed not have functionality of runtime re-configuration without
> restarting. Some of the functionality can be done through mod_perl, and
> surely most of the functionality can be done with addon module.
>
> However adding or removing of module usually causes reconfiguration of
> co
> > * it's not terribly safe to modify the configuration structures created
> > by httpd, they really are applied in a serial manner, not as some state
> > machine the config state. Most platforms couldn't unlink a module and
> > replace it with the same (new build) of a module even
> * it's not terribly safe to modify the configuration structures created
> by httpd, they really are applied in a serial manner, not as some state
> machine the config state. Most platforms couldn't unlink a module and
> replace it with the same (new build) of a module even if you t
Pravin wrote:
>
> If this is the way Apache implements its plug-in architecture then
> why do we need to restart Apache when we add new module
> or update existing module ?
Three reasons;
* fork() lets us create, say, 25 or 500 children, each identical, each
with a copy-on-write pointer to
Hi,
Following is my understanding, and please correct me if I am wrong
anywere.
As per my understanding Apache uses plug-in architecture to increase
its functionality at runtime. For this, it uses modules
which are in form of DSO's (Dynamic shared objects) (ie. .so .dll
etc...).
And it uses dlsym
