I just asked a friend of mine who is using Pair if he could dl()
modules. Pair give users their own extension_dir, but no access to
php.ini, and no way of reloading the server (which would still be
required for an auto-load extension dir). So for Pair users, dl() is
currently the _only_ way to load third-party extensions.
The reason Pair do this, according to my friend, is that in case Apache
crashes, they will at last know what modules were loaded for all
processes, only the processes that run PHP scripts doing dl() will crash
because of bugs in the 3rd party extensions.
Following this train of thought, an auto-load extension folder would not
be a solution either, because it would still lead to the additional
vulnerability to Apache processes that Pair avoid this way.
I think we should bring in some people from hosting companies into this
discussion, to make sure we have all the facts right. Right now we are
assuming a bit too much.
- Stig
On Tue, 2002-03-12 at 12:01, Zeev Suraski wrote:
> That sounds like a pretty good idea, actually :)
>
> Zeev
>
> At 11:32 AM 3/12/2002, Stanislav Malyshev wrote:
> >MK>> For them, digging into the guts of the system, installing PHP
> >MK>> extensions there and modifying obscure, Apple-supplied configuration
> >MK>> files is MUCH, MUCH more frightening than just downloading a php
> >MK>> extension, dropping it into the Sites folder in their home directory,
> >MK>> and calling dl("extension.bundle"); in their PHP scripts.
> >
> >Might the solution be in the form of some 'auto-load extension folder'?
> >I.e., folder in which all extensions found there are loaded automatically?
> >
> >--
> >Stanislav Malyshev, Zend Products Engineer
> >[EMAIL PROTECTED] http://www.zend.com/ +972-3-6139665 ext.115
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
