Pádraic Brady has a quick update today pertaining to the PHPSecInfo project - a new manual (currently in development).

I'll keep adding to it over the days, weeks and months ahead. The current form is going to be mainly a draft. When it's done, I'll go through it and do some serious editing. Next priority is getting in the material on actually using and implementing PHPSpec...

You can find the manual at http://dev.phpspec.org/manual/ with quite a bit of content already filled out. Topics currently covered include installation guides, your "first steps", testing the code and some examples of it in use.

Since it's been moved up into the "Final Draft" stage in its proposal process, Padraic Brady wanted to blog about this latest update for the OAuth Specification, a standardized protocol that allows secure API authentication from both desktop and web applications.

Because I love all things OpenID related and am an OpenID "pusher" in Europe (blame the OpenID Europe Foundation membership on Snorri Giorgetti), I'll be proposing a PHP5 implementation of OAuth to the Zend Framework (assuming no other OAuth proposal) and PEAR (PEAR because that's now the home of my OpenID For PHP library under proposal).

You can get more information about OAuth from the project's website.

Soenke Ruempler has posted today about something they found a need for in their group and wanted to create something they could share back with the community when it was done - a Message Queue System developed in PHP.

You'll find a Draft for a php-based messaging system below. We'd be glad if we get some comments from the readers. Because we're heavily using open source we want to give something back to the community and make the message queue system open source. And, yes, if someone is planning something like this or already knows a solution, please let us know, too. We don't wanna reinvent the wheel!

He fleshes out the proposal by describing it in three sections - the problem the need came from, some of the existing solutions the web has to offer (including the Java Message Service and IBM's XMS messaging) and the actual draft of the implementation including the architecture, scalability, a name (none yet) and where they're going from here.

To get himself more familiar with the whole MVC scene, Jacob Santos has decided to jump in feet first and work up his own controller class to see how things work.

I've decided it would have been a mockery to PHP developers, if I had taken up writing about MVC, which I still barely know anything about. However, I have been working a little bit with Page Controller Pattern of MVC. I decided I could write what little I do know and let someone with more knowledge fill in the blanks. Helping myself and others in the community.

He looks at the types of page controllers (if blocks, directory, and object methods) and, for each, provides a simple code example (with the exception of the object method) to give a clearer picture of what a controller does.

He also includes an update to the post that points to Cgiapp2 as exactly what he was looking for in his MVC mission.