Anyone have experience porting a DCOM architecture to a .NET Remoting architecture? I am looking for the appropriate alternative to DCOM in .NET land, and it looks like .NET Remoting is the way to go.
Comments?
Printable View
Anyone have experience porting a DCOM architecture to a .NET Remoting architecture? I am looking for the appropriate alternative to DCOM in .NET land, and it looks like .NET Remoting is the way to go.
Comments?
Try XML Web Services. I am not well versed with it, but it does have its advantages. .NET Remoting would be faster over a network, but XML Web Services are platform independent. Also, XML can be passed across on TCP.
I failed to mention that I have thoroughly investigated Web Services and the paradigm is inadequate to replace DCOM as a messaging architecture.
Ie.. a web services solution cannot "push" information down to the client (like raising an Event). Rather, the client asks for information, and he gets it. Somewhat like a sneeze.
I think .NET Remoting is the way I have to go. I am getting some books on the topic in the coming week.