You’re correct on the typo.

The separation is the execution and “genericism” (a little G W Bush for ya).

Yes, if the $_commands array is empty, we don’t want to attempt to execute the foreach loop.

Clayton, would you be interested in joining the alpha dev team? If so, shoot me an email.

Also in your example there’s ‘if (count($commands) > 0)’ I assume this is a typo and should be ‘if (count($this->_commands) > 0)’. In which case, is the if statement required as the foreach wont execute if the array is empty.

Btw I’m looking forward to your Fever Framework.

The Observer, on the other hand, has specific attributes. You may have an observer that is specific to database events, service events, etc. This can also get confused with the Decorator pattern.

The Decorator is actually closer to CoC than Observer. Rather than executing until an object handles something, the Decorator iterates over all objects to format functionality. Logging is a good example.

$log = new Logger();
$log->addLogger(new FileLogger($file_name));
$log->addLogger(new DBLogger($db_conn));
..
..
..

$log->log(‘error’,'This is an error!’);

The above logs a single request to multiple sources via a single interface.

Looking at it, it would look very similar albeit with a different name.

The basis of both is you have subject and a subscriber. A subject acts as a publisher and a subscriber receives updates from that publisher.

$observer = new Observer();

// You could optionally specify the nature of the subscription, in the second argument
$observer->subscribe(new Mailer());

// This essentially runs the command
$observer->publish(‘mailer’, array(‘address’ => ‘you@and.me’));

Another example often seen involves the use of events and triggers.
$observer->addEvent(new Log());
$observer->trigger(‘error’, array());

The public beta will be available in a couple of weeks.