configure wcf away sometimes

Hi

say I develop a "backend" system which exposes functionality via WCF - a
client running elsewhere can then use WCF to talk to my program.

But if I later install the client on the same physical machine as my
backend, can I configure WCF to "disappear"? I mean, can I somehow easily
avoid the overhead of the network communication by configuring WCF to
directly call my backend classes (as all the program code - client and
server - is sitting together) instead of using proxies and network
communication?

(The client and backend are both programmed in .net/c#).

Thanks,
Peter

Peter,

In the same box, you can use the named pipes binding (netNamedPipeBinding)
or netTcpBinding, or if in the same executable try the Null Transport
binding. Just expose a new endpoint with the chosen binding.

More info on NullTransport here:
http://weblogs.asp.net/cibrax/archiv...t-for-wcf.aspx

Tiago Halm