Re: [PHP4BETA] Dynamic verses static install
| From: | php4 at developersdesk dot com | Date: | Thu, 11 May 2000 19:15:59 +0000 |
| Subject: | Re: [PHP4BETA] Dynamic verses static install | ||
| Groups: | php.version4 | ||
| Request: | Send a blank email to php-version4+get-14867@lists.php.net to get a copy of this message | ||
Addressed to: "Jason" <jay1@swift-web.com>
php4beta@lists.php.net
** Reply to note from "Jason" <jay1@swift-web.com> Thu, 11 May 2000 15:49:58 -0700
>
> I'm installing the new php4-0CR2 on a Linux box and am confused as to
> the difference between a dynamic installation and a static
> installation? Can anyone help me on this one? Thanks Jason
>
In a dynamic installation various add-ins to Apache are stored in
separate files and linked at runtime. Dynamic, DSO, or APXS
installations (all the same thing) allow you to install or upgrade parts
of Apache without having to re-compile everything. You can manage the
modules that Apache loads from the config file (LoadModule,
ActivateModule) and update modules without having to compile other
modules or Apache.
A static install puts everything in one big file. Any time you change
any part of your web server you end up compiling all of it. (Make often
skips much of the work.) I actually prefer this for my servers. I can
release a new web server with mv httpd httpd.old then a copy that
puts the new program in the right place followed by killing and
re-starting the server. I never have to worry about module mismatches,
or what if a file is missing from the module library.
I am in the unusual position of wanting to maintain a large number
(currently 4) web servers with the same software, so the idea of a
single file upgrade is appealing to me. I am using mod_ssl and have not
yet got it working DSO, but static worked the first time I tried it, and
many more since.
YMMV.
Rick Widmer
http://www.developersdesk.com