Re: PEAR in PHP 4.3.0
| From: | Gabor Hojtsy | Date: | Sun, 29 Sep 2002 07:29:35 +0000 |
| Subject: | Re: PEAR in PHP 4.3.0 | ||
| References: | 1 2 3 4 5 6 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-9672@lists.php.net to get a copy of this message | ||
> > > Using php.ini is not very good because this is (atm) a global
> > > setting and cannot be personalized (IE a per host settings).
> >
> > It can be, if you run Apache ;) php_value, php_flag and the like.
>
> btw, that s a fact I m always bored with. The world is not only a
> linux/apache/mysql world, afaik :-).
BWT the fact that Apache supports this would have already drived
other server/SAPI authors to support something like this. The fact
that it's not supported means that either the server/SAPI
maintainers don't care or have no time for this stuff (vhosts
based configuration). Anyone who uses Apache with vhosts knows
that vhost based configs are the greatest thing you can get.
I would not like to start any flames here, don't misunderstand me.
You are right that it's annoying, that many guys out there think
that it's an Apache only world (hey I am also using it on windows ;),
and that the settings needs to be portable.
So then why to put the settings into the registry, as then you
cannot just copy your program and settings to another machine,
keeping in mind, that if you move that generated .reg file it *may*
not be the exact thing from the registry (registry could have been
modified after addign that reg file)?
Windows registry is kind of a black magic thing for many guys
out there, and things like how to export settings from the registry
to move your setup to another computer may not be easy, and will
drive the way to more and more support questions IMHO.
Goba