Re: Re: cvs: pear /Event_Dispatcher Dispatcher.php Notification.php package.xml /Event_Dispatcher/examples bubbling.php cancel.php
notification-class.php object.php /Event_Dispatcher/tests Console_TestListener.php Dispatcher_testca

From: Date: Tue, 08 Feb 2005 08:58:01 +0000
Subject: Re: Re: cvs: pear /Event_Dispatcher Dispatcher.php Notification.php package.xml /Event_Dispatcher/examples bubbling.php cancel.php
notification-class.php object.php /Event_Dispatcher/tests Console_TestListener.php Dispatcher_testca
Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-36042@lists.php.net to get a copy of this message
Alan Knowles wrote: >My first thoughs would be making it PEAR_Event_Dispatcher - as most >other infrastuctural classes in the same ilk are currently there: >eg. PEAR_Error / PEAR_ErrorStack / PEAR_Exception.. If we go this route, people might be scared about PEAR becoming some kind of framework with lots of requirements. And as Event_Dispatcher doesn't extend PEAR, this might also surprise them. >Otherwise, I cant really see any alternative to creating a Event >Category. (which may not be a bad thing).. I think this could do, especially because there might be other packages there in the future (example: remote notifications, distributed notifications, event queue, etc.). Who could create such a category ? Martin ? Thanks, Bertrand Mansion Mamasam

« previous php.pear.dev (#36042) next »