RE: [PHP4BETA] PHP 4.0b3 released

This is A Good Thing. Instead of duking out whether or not things like DB Abstraction are good or not, just make a shared library system, and let those who want it, use it. Would it be worth it to work in some kind of public key signature to the modules (that the PHP engine would check)? With a scripted language, it's nice to know that you are looking at the original module as the author has intended it, or if it's been modified along the way to you....just a thought. Of course, the check could always be overridden by a script or php.ini directive. -jason Samuel Liddicott <sam@campbellsci.co.uk> on 11/18/99 08:38:18 AM To: rwidmer@developersdesk.com, Stanislav Malyshev <stas@zend.com>, php4beta@lists.php.net cc: bcc: Subject: RE: [PHP4BETA] PHP 4.0b3 released > -----Original Message----- > From: rwidmer@developersdesk.com [mailto:rwidmer@developersdesk.com] > Sent: Friday, November 19, 1999 04:40 AM > To: Stanislav Malyshev; php4beta@lists.php.net > Subject: Re: [PHP4BETA] PHP 4.0b3 released > > I think a _system wide_ shared library would be an asset to PHP. Yes. > I have a couple of > libraries I want to make available to all the virtualvhosts on my > machine without > turning off safe mode, Yes. > and I hope to make quite a few more. I > think the same thing > for data files would be good too, but I could live without it. If > the PHP community > had a shared library available you would soon see a collection of > utilities like the > Perl module library. I think so. > I think this would be a very easy way to provide shared libraries. No new > configuration options are needed. (Maybe just one, to turn it of > and off.) Once safe > mode has been modified it works like this: Maybe another which specifies owners of the shared libraries. In effect it becomes a modification to safe mode, an "also-allow" option, as well - so files owned by "also-allow-users" users can be included/requried/etc into scripts in safe mode. > I don't care how it happens, I just want to see some kind of > system wide shared > library that anyone can use with safe mode on. Yes. > I want very tight > control over who can > add files to the library, which is why I suggest it must be done > by root. Maybe you > should be able to select some other user in php.ini, but I look > at maintaining this > library to be similar to installing the web server, not something > for an ordinary > webmaster. If we're lucky, someday there will be a couple hundred > standard libraries > that almost everyone has on thier systems. > > If _anyone_ has ideas on this, I'd like to hear them. Well I love you idea. If phplib used it, I would love it a lot more. Sam -- PHP 4.0 Beta Mailing List <http://www.php.net/version4/> To unsubscribe, e-mail: php4beta-unsubscribe@lists.php.net For additional commands, e-mail: php4beta-help@lists.php.net To contact the list administrators, e-mail: php4beta-admin@lists.php.net