You already know Singleton, Signal/Observer, Factory and friends. But, which object oriented patterns are en vogue in the PHP world and how can you seize their power? This talk gives you an overview on Dependency Injection, Data Mapper and more OO patterns the PHP world talks about right know, using practical code examples.

You can listen to this latest episode either via the in-page player or by downloading the mp3 directly. You can follow along with the talk in his slides over on the qafoo.com site.

The three patterns are from Martin Fowler's Patterns of Enterprise Application Architecture book:

• Unit of Work - maintains a list of objects affected by a business transaction and coordinates the writing out of changes and the resolution of concurrency problems.
• Identity Map - each object gets loaded only once by keeping every loaded object in a map
• Lazy Load - object that doesn't contain all of the data you need but knows how to get it.

This book is absolutely jam-packed with information useful to the medium-advanced PHP coder. SPL is described over a few chapters, and a quick intro to Zend's MVC framework is provided. Of particular interest to me were the final chapters, to do with certificate-based authentication, and a chapter near the beginning describing the upcoming features of PHP6. Great book - I really enjoyed it.

The review gets into detail on some of the chapters and some of the shortfalls that Kae saw about them. Things like:

• The title says "frameworks" but only one is really discussed (Zend Framework)
• The testing/continuous development sections weren't long enough
• The "web 2.0" section was a little sparse
• The only real web service protocol talked about is SOAP.

Overall, though Kae found the book to be worthy of a place on any developer's shelf.

So today you get a double bonus. You get to check out Pro PHP, Patterns, Frameworks, Testing and more by Kevin McArthur. You also get a great tutorial on SPL!

The sample chapter looks (obviously) at the SPL, the Standard PHP Library - functions included with PHP5 releases to accomplish some pretty cool things.

As an application developer, you can have a lifelong career without ever knowing what any of the patterns are called or how or when they're used. However, I've found that a good working knowledge of these patterns, as well as those introduced in the developerWorks article "Five common PHP design patterns" (see Resources), allows you to do two things: Enable high-bandwidth conversations and reduce painful lessons.

The patterns they talk about in this "five more" article of the series are:

• Adapter Pattern
• Iterator Pattern
• Decorator Pattern
• Delegate Pattern
• State Pattern

Diagrams are provided for each of them, showing how they flow along with brief code examples (structures really) to show how that transitions over to actual use.

Originally, I planned to write about how to configure the Apache server to run both PHP4 and PHP5. With the push toward PHP5 (see Go PHP5), there are now hundreds of articles covering that topic. Instead, I will talk about two IT patterns I use for PHP development on Windows. The patterns are ancient and familiar to most Unix developers, but little used in the Windows world.

He uses something he calls "junction points" to make both of the patterns work and describes a bit about what they are and how to create them. Then, it's on to the descriptions - he covers what each of the patterns is about and includes a method for implementing it. The Bait-and-Switch is mostly about swapping out multiple software versions transparently and the Shell Game uses a shell script to handle the creation of the environment and the execution instead.

Coming out on top with 33.3% of the votes is "Folks who follow design patterns religiously are missing the point" - an interesting choice for most of the developers out there. Design patterns can be one of the most useful bits of functionality in an application if used right. The option, however, is a bit vague - do they mean that they only use design patterns in their code or that they use them at all?

There was a tie for second place between the "Other reasons" and "Classes and inheritance are not new to PHP 5" options. Pulling up the rear with only 5.6% of the votes was the last option, "Managing state between pages is very straight forward in PHP".

Be sure to check out and vote in this week's poll (a bit better subject matter) that asks the question "Why Does PHP Suck?".

I seized the time on the tram yesterday night to take a look at it and I have to admit I'm quite impressed. Stephan managed to write down a lot of practical experience in respect to the implementation of OO patterns with PHP.

Tobias talks about the structure of the book (recommending it to anyone looking to learn OOP in PHP), and mentions some of the chapter topics including:

• New OOP features in PHP5
• Basic OOP concepts
• Generation Patterns (Singleton, Factory, etc)
• Behavior Patterns (Subject/Observer, Visitor, Iterator)

While some books only touch the theory of design patterns and avoid giving practical examples to the user, Stephan manages very good to combine both.

After nearly a year of work, my first very own book has finally been published and arrived last weekend.

PHP Design Patterns is published by O'Reilly and introduces the reader to the world of patterns by providing practical examples.

One small note, though - the book is written in German, so English-only readers might not find this the book for them. If you want more information on the book, though, you can check out its website for full details and some code examples.

This chapter provides an overview of the advanced OO features now available in PHP. Some of the examples developed here will be used throughout the rest of this book and will hopefully serve as a demonstration that certain problems really benefit from the OO approach.

The article lays down the foundation for the more complex information to come. It introduces object-oriented programming briefly, and talks about some of the handy features of it - like inheritance, static attributes and methods.