all groups > dotnet distributed apps > january 2006 >
You're in the

dotnet distributed apps

group:

pattern for switching between local and remote objects?


pattern for switching between local and remote objects? Jay A. Ritchie
1/20/2006 1:46:02 PM
dotnet distributed apps: Does anyone have a pattern reference that would allow me to dynamically
switch between instantiating local objects v. remote objects? I'm
particularly interested in anything that uses WCF to manage the remoting
options.

Re: pattern for switching between local and remote objects? Michael Nemtsev
1/21/2006 6:49:09 PM
Hello Jay,

Look at the InvensionOfControl pattern, if I undestood u correctly
http://www.martinfowler.com/articles/injection.html

JR> Does anyone have a pattern reference that would allow me to
JR> dynamically switch between instantiating local objects v. remote
JR> objects? I'm particularly interested in anything that uses WCF to
JR> manage the remoting options.
JR>
JR> Thanks.
JR>
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/members/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche

Re: pattern for switching between local and remote objects? Jay A. Ritchie
1/27/2006 11:41:02 AM
[This followup was posted to microsoft.public.dotnet.distributed_apps
and a copy was sent to the cited author.]

In article <9cc1c863750858c7eceba4955004@msnews.microsoft.com>,
nemtsev@msn.com says...
[quoted text, click to view]
Michael-

How does this compare to just using a factory pattern? Couldn't the
factory just return the correct object (local object or proxy for remote
object)? What more do the inversion of control pattern implementations
(dependency injection or service locator) add?

-Jay
























































































































































Re: pattern for switching between local and remote objects? Michael Nemtsev
1/27/2006 6:52:05 PM
Hello Jay,

Read here http://msdn.microsoft.com/msdnmag/issues/05/09/DesignPatterns/
Hope it helps.

Factory relates more to the single application design (GOF wrote abt apps
that hardly overcome boundaries)
Now, the distribution fashion shift aspects of design and conventional patterns
need to be reviewed a bit.

[quoted text, click to view]

JR> How does this compare to just using a factory pattern? Couldn't the
JR> factory just return the correct object (local object or proxy for
JR> remote object)? What more do the inversion of control pattern
JR> implementations (dependency injection or service locator) add?

---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/members/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche

AddThis Social Bookmark Button