Proxy Pattern

Hi all,

I've been reading about the Proxy Pattern and it seems like just normal encapsulation to me or do I misunderstand it?

To me, Proxy looks like using a "middleman" class to delegate requests to the actual class so that the implementation of the actual class is hidden from the user.

Another benefit of this proxy pattern is that can delay the creation of an object from the actual class until you need it.

That is what I understand from what I read about it, but do you know some scenarios where you would use the proxy pattern?

Is it for example useful to separate the GUI from the actual code?

grtz

[650 byte] By [dfvdfvdfvxfva] at [2007-11-27 8:43:22]
# 1

The Business Delegate design pattern is a version of the Proxy pattern.

A Presentation-tier Business Delegate delegates method calls to the Business tier.

The code on the Presentation tier only contains references to the business delegate. There are no class/code level dependencies between the business model implementation and the code on the Presentation tier.

GhostRadioTwoa at 2007-7-12 20:43:02 > top of Java-index,Other Topics,Patterns & OO Design...