Re: Merging PHPLIB into PEAR

Quoting Ulf Wendel <ulf.wendel@phpdoc.de>: > PEAR lacks solutions for sessions, permissions, authentification, > templates... I'll agree on templates. I don't see what kind of support PEAR _needs_ for sessions - what does the phplib session class do that the php4 native functions don't do? I'm of the (certainly arguable) opinion that authentication and permission classes don't belong in PEAR itself. See below for more. > I like most of PEAR, but beside the DB abstraction there're no classes of > real importance. That's a rather arbitrary statement, isn't it? For one thing, it ignores PHPDoc, though whether or not that should be in PEAR is another matter; for another, there are plenty of classes which if you had a need for them might be very important. > 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. =) -chuck -- Charles Hagenbuch, <chuck@horde.org> Entropy. It's what's for dinner.