Comments for PHP Design Patterns

Comment on PHP Chain of Responsibility : Making a Selection by nbari

nbari — Fri, 19 Aug 2011 09:04:41 +0000

This pattern could be an alternative to use many if /else / else if, with classes in cleaner way.

Excellent article.

Comment on PHP Proxy Design Pattern: Protect Your Assets by Ing. Armando Ibarra

Ing. Armando Ibarra — Thu, 18 Aug 2011 22:34:04 +0000

Hi!

I use the proxy design pattern to control access to the functions of the web application, using ACL ‘s. In order to control every operation you can perform the user.

In my opinion I think it’s best to use the interface instead of abstract class, because as you say if you get more safety data connection to the database, but if another developer creates a class:

How do you do to control that actually implements the proxy?

Comment on PHP Decorator Design Pattern: Accessorizing Your Classes by Abba Bryant

Abba Bryant — Wed, 30 Mar 2011 04:55:29 +0000

And by the way, awesome blog.

Comment on PHP Decorator Design Pattern: Accessorizing Your Classes by Abba Bryant

Abba Bryant — Wed, 30 Mar 2011 04:54:59 +0000

Looks like maybe a bad copy paste on the concrete component classes. It would seem that the first example is setting the description member variable correctly but fails to implement IComponent by not having a getComputer method. It does have a getDescription method.

The second example has a correct getComputer method but is setting the computer member variable to what should be it’s description.

Comment on PHP Decorator Design Pattern: Accessorizing Your Classes by Shane Edwards

Shane Edwards — Mon, 28 Mar 2011 15:27:05 +0000

Hi,
I’ve enjoyed reading your article. Please forgive me if I’m wrong, I’m not an experienced programmer but wouldn’t the line in the client constructor: print $this->computerNow->getComputer() return null for a new Dell() object?
Shane

Comment on Private Methods in PHP by William Sanders

William Sanders — Mon, 18 Oct 2010 18:19:56 +0000

Hi Yehosef,

Great question. I like to use private variables/functions whenever possible to insure encapsulation. If I have an abstract class where I know I will be subclassing a lot, I’ll use protected methods/variables.

You can use privately declared variables in protected methods or even public methods. For example,

^?View Code PHP

private $foo;
 
public function bar()
{
   $foo="hello";
   return $foo;
 
}

Kindest regards,
Bill

Comment on Private Methods in PHP by Yehosef

Yehosef — Mon, 11 Oct 2010 11:39:46 +0000

Do you have any insights on when to use private vs protected methods? The problem is private is extended classes don’t have access to them. It seems there may be some cases in which this is desirable, but that most time protected is a better choice. Do you have some guidelines?

Comment on PHP Proxy Design Pattern: Protect Your Assets by William Sanders

William Sanders — Sat, 25 Sep 2010 08:13:02 +0000

Hi Albert,

Sorry I haven’t responded until now, but I’ve been busy with different projects I’ve had to take care of. Soon I hope to have lots more for this blog and try to move through all of the PHP design patterns,

Kindest regards,
Bill

Comment on PHP Proxy Design Pattern: Protect Your Assets by Albert

Albert — Mon, 13 Sep 2010 21:50:06 +0000

Congratulations, it’s very interesting article. I’ve read your articles about design pattern and are very interesting. I look foward to reading the next.

Comment on PHP Proxy Design Pattern: Protect Your Assets by Tweets that mention PHP Proxy Design Pattern: Protect Your Assets | PHP Design Patterns -- Topsy.com

Mon, 07 Jun 2010 13:56:39 +0000

[...] This post was mentioned on Twitter by Bill Sanders, Bill Sanders. Bill Sanders said: PHP Proxy Design Pattern: Protect Your Assets http://bit.ly/dBNJYw This is all PHP but pretty easy for any language. Working on AS3 version. [...]