WCF vs. .NET Remoting in intra-machine services

Are there any recommendations regarding the use of WCF in intra-machine
services?

I find it difficult to justify WCF for a significant (read: multiple
interface inheritance, multiple levels of events and multiple levels of data
types) service in intra-machine services compared against .NET Remoting. In
particular, if you're interested, I'm porting an implementation of JTAPI, a
telephony specification, to .NET.

Regards

--
What difference does it make to the dead, the orphans and the homeless,
whether the mad destruction is wrought under the name of totalitarianism or
the holy name of liberty or democracy?

-M. Gandhi

check http://msdn2.microsoft.com/en-us/lib...57(VS.80).aspx
Arkady

"Javier Estrada" <jestrada@discussions.microsoft.com> wrote in message
news:CBDF920C-4DD2-427E-BEB2-DBD5DD6176C2@microsoft.com...
> Are there any recommendations regarding the use of WCF in intra-machine
> services?
>
> I find it difficult to justify WCF for a significant (read: multiple
> interface inheritance, multiple levels of events and multiple levels of
> data
> types) service in intra-machine services compared against .NET Remoting.
> In
> particular, if you're interested, I'm porting an implementation of JTAPI,
> a
> telephony specification, to .NET.
>
> Regards
>
> --
> What difference does it make to the dead, the orphans and the homeless,
> whether the mad destruction is wrought under the name of totalitarianism
> or
> the holy name of liberty or democracy?
>
> -M. Gandhi

Arkady,

I'm not trying to migrate from .NET Remoting to WCF. I'm trying to decide
whether to use .NET Remoting or WCF on a new design.

The project is not a simple one, since JTAPI has multiple orthogonal layers
of functionality in the form of interfaces.

I know how to represent this model in an OO architecture, but I had been
struggling to transition it to SOA because of the orthogonal layers. I was
trying to provide a very similar model in WCF that would have involved
service contract inheritance, callback contract inheritance, data contract
inheritance, etc., that would not have been very practical on the client side
(no bang for buck).

I'm past that point, and I appreciate your response.

You could use named pipes as your protocol, and declare the ServiceKnownTypes to show your hierarchy.

Gracias, Armando.

During the analysis there were other problems that we won't be able to solve
with WCF (it is simply the wrong tool for this project) so we decided not to
pursue it further.