Re: Merging PHPLIB into PEAR

Hello Chuck, On Wed, Jan 17, 2001 at 22:51 -0500, Chuck Hagenbuch wrote: > > > Let's look forward how we can add the PHPLib to PEAR to build an > > "application framework" (in the sense as PHPLib is one) that makes PHP 4 > > even more powerful. > > I don't think that this is necessarily a good idea. An application framework > dictates a specific philosophy of application design on the people writing > applications. Things like permissions and authentication, no matter how > generically written, dictate some model of permissions, some model of > authentication - and users - to people that simply is not going to work for > everyone. Binarycloud is an application framework. Horde is at least part of an > application framework. Horde builds on _top_ of PEAR, but I'm not going to go > committing the Horde preferences code to PEAR - it's one way of doing it, but > it's such a variable thing that it probably wouldn't make sense for people who > weren't interested in more of Horde. However, I _have_ contributed the Log > classes, HTTP_Compress, and other classes that we wrote that solve simple, > smaller problems that people can build on. Even the Log classes are debatable, > btw. > > I'm not sure if I'm articulating my ideas very well, and I don't know if anyone > else agress with me. But I'm curious either way. =) Having thought over the design of an authorization framework, I tend to agree with Chuck. I mean, I can implement it, but it isn't going to be the single design in the universe useful to everyone. To follow an objective not to turn PEAR into an ordinary overgrown code bin (hey, but isn't CPAN like this?), such things are better left to particular application frameworks and site-specific code bases. -- Stay tuned, MhZ mailto:mookid@sigent.ru ----------- The best thing about growing older is that it takes such a long time.