Hi!
Let me simply ask, do you think there is technical merit (worth while) to create a patch which offers multi-directory DLL loading support for the PHP.INI extension_dir= option?
extension is an one-time configuration directive. Since it allows full path now, how hard would it be to get it right with full path? Multiple paths may contain some dangerous pitfalls - like, what happen if extension is in multiple paths, and in some it's not compatible (wrong version/debug/ts)? What if you have some old version lying around in fifth path, and you had new version in first path, but somehow permissions got mangled and it's not readable, so wrong version is loaded? Etc., etc. - it seems to have potential for many unpleasant moments.
1) Reduce extension DLL (non-PHP related) dependency issues,
How? I'd say, if you have extension A using foo.dll, and extension B using foo.dll, and they live in different directories, don't you now have to maintain two copies of foo.dll instead of one?
2) Better support for PHP integration with Application Servers, and
Here I'd like to hear more - how it helps PHP and Application Servers?
3) Better support for security isolation, sand-boxing applications
I'm not sure how giving multiple places to put security-sensitive stuff (extension has access to everything) improves sandboxing, could you explain?
-- Stanislav Malyshev, Zend Software Architect [EMAIL PROTECTED] http://www.zend.com/ (408)253-8829 MSN: [EMAIL PROTECTED] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
