Re: [PEPr] Comment on Util::Util_Observable

Pepr wrote:

Philippe Jausions (http://pear.php.net/user/jausions) has commented on the proposal for Util::Util_Observable. <snip>

So the dilema is multifaced: 1. Should PEAR host interfaces? (IMHO, yes)

I think yes too. They bring a lot to PEAR, particularly in terms of flexibility & interoperability.

2. Are interfaces framework stuff? (yes)

Yes, they are. However, I think it's important to note that PEAR is already doing framework stuff in a far less flexible way. Basic "glue" tools like PEAR_Error, Log, DB make PEAR packages very inter-dependent. The problem isn't that PEAR provides a framework, but rather that w/ PHP4 that framework was forced to be very inflexible.

3. Should PEAR host/recommend pattern design intefaces (why not? factory, singleton got pretty much standardized, even though not written into an interface) Although only most widely used patterns like the subject/onserver should be accepted, and with at least one package implementing it. - Is PHP5 too new for PEAR to make a decision... (IMHO, no, better make PEAR the leader)

Yeah, I think some interfaces -- especially this listener interface is a good example definitely belong in PEAR. It's obviously very generic; putting it in a Pattern category might make sense. I also believe that creating an Interface category doesn't make sense, because there are potentially as many interfaces as packages (not that there should be 1-1 correspondence, but just in terms of possibilities). Hans