PHPDeveloper.org

Matthew Weier O'Phinney's Blog: A Simple PHP Publish-Subscribe System

Tue, 16 Dec 2008 10:23:26 -0600

In a new post to his blog Matthew Weier O'Phinney shares a simple publish-subscribe system he's created based on a feature of the Dojo toolkit using the Zend Framework to create an easy notification architecture.

The system has elements of Aspect Oriented Programming (AOP), as well as the Observer pattern. Its power, however, is in the fact that an individual object does not need to implement any specific interface in order to act as either a Subject or an Observer; the system is globally available.

The script creates an object that publishes an event. This event then sends off messages to all of the other objects subscribing to it. A code example is included. You also can check out the code from its page on github (as a part of his Phly libraries) and play with it yourself.

Matthew Weir O'Phinney's Blog: Phly Darcs Repository online

Tue, 06 Jun 2006 06:19:50 -0500

Matthew Weir O'Phinney has this note for those working with the Phly PEAR channel - he's added a darcs repository to manage the contents of the channel.

If you're not familiar with darcs, it's a revision control system, similar to GNU Arch and git; changes are kept as patch sets, and repositories are branched simply by checking them out. This makes darcs repositories very flexible, and incredibly easy to implement. Static binaries are available for most systems, which makes it easy to install on systems to which you have no administrator rights.

There's also a web-based interface to it that uses Perl/XML/XSLT to create it, but he found it a bit constrictive and not customizable at all - so he ported it to PHP (using Cgiapp2), the result being Phly_Darcs.

Matthew Weir O'Phinney's Blog: PHP Library Channel

Tue, 16 May 2006 06:00:08 -0500

Matthew Weir O'Phinney has posted this new item on his blog today, a look at his creation of a new PEAR channel (found here) where he's started work on a general use PHP library repository.

I've been working on Cgiapp in the past few months, in particular to introduce one possibility for a Front Controller class. To test out ideas, I've decided to port areas of my personal site to Cgiapp2 using the Front Controller. Being the programmer I am, I quickly ran into some areas where I needed some reusable code -- principally for authentication and input handling.

So what did I choose? To reinvent the wheel, of course! To that end, I've opened a new PEAR channel that I'm calling PHLY, the PHp LibrarY, named after my blog.

Some of the targets of his project include:

Loosely coupled; dependencies should be few, and no base class should be necessary.
Designed for PHP5 and up; all classes should make use of PHP5's features.
Tested; all classes should have unit tests accompanying them.