Re: RE : [PHP-DEV] Re: What's wrong with dl?
| From: | Richard Lynch | Date: | Thu, 28 Sep 2006 19:08:05 +0000 |
| Subject: | Re: RE : [PHP-DEV] Re: What's wrong with dl? | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-25869@lists.php.net to get a copy of this message | ||
On Mon, September 18, 2006 6:20 am, LAUPRETRE François (P) wrote:
> OK. Thanks for your answers, I didn't see this problem with each
> thread restarting in an 'empty' state and having to reload extensions
> through the autoloader. Even if loaded extensions could be registered
> in shared memory, I agree: it is much better to remove dl() except in
> CLI mode.
In multi-process non-threaded SAPIS can we not keep dl()?
Obviously it has to die in threaded SAPIS, and I can see why that is
so. [shudder]
But if somebody is running Apache pre-fork whatsit...
Why remove it from SAPIS that can support it?
I actually found it very useful to be able to dl() an iffy extension,
knowing that the odds that I'd bring down a whole server just to play
with it were smaller that way. Yes, a dev server. Even so -- I've
got a lot of balls in the air, and was fairly confident the extension
was "safe" and wanted to test it without building a whole new server
or yet another port/vhost to keep track of.
For an extension that's rarely rarely rarely used, like almost never,
dl() makes perfect sense, in an environment that can support it.
--
Like Music?
http://l-i-e.com/artists.htm