Re: When Symbian met Design Patterns (2) -- Proxy Pattern

stonechm — Tue, 17 Jul 2007 05:23:30 +0200

Very wonderful article. But I think the metaphor is not exactly.
I think that one key point about proxy pattern is that the Proxy is from the end user(or client) view.
So in the example above, we should take the EndUserView as the postoffice, CRemoteInfProxy as Mike and CRemoteInfImp as Ben.
The postoffice wants to deliver newspaper, so it interact with Mike, but Mike will not do the job himself, he will outsource the job to Ben and Ben is the one who does the real job.
So from this point of view, the literal will be consistent with the class diagram.

When Symbian met Design Patterns (2) -- Proxy Pattern

rensijie — Tue, 24 Apr 2007 17:00:33 +0200

If you had seen the show "Growning Pains" you must remember in one episode, Mike got a newspaper delivery job and he didn't want to deliver any of the newspapers. So he "outsourced" those newspapers to his brother Ben. And the postoffice gave Mike about 5 bucks but Mike only gave Ben 2.5 bucks for remuneration, so he could get 2.5 bucks without doing anything. In postoffice's perspective, they gave Mike 5 bucks and 100 newspapers and no matter how Mike delivered those newspapers, as long as newspapers are sent on time, they will pay for Mike next time anyway(actually he messed it up in the end...). That is, the way Mike deliver newspaper is transparent to the postoffice. Mike could do it himself or let Ben to do this, or maybe Ben will also "outsource" his job to others, whatever.

NewLC - When Symbian met Design Patterns (2) -- Proxy Pattern - Comments

Re: When Symbian met Design Patterns (2) -- Proxy Pattern

When Symbian met Design Patterns (2) -- Proxy Pattern