All geek questions in one place

Is there a viable counterpart to DCOM in .NET?

I know that .net has WCF, which I think was touted as a replacement for COM when it was codenamed Indigo (?), But is it really suitable for use in a .NET application, providing the same functionality, What is C ++ / DCOM?

The DCOM application on the client-server system can be painful, but I think it is quite effective compared to other parameters, such as web services, which in any case have other problems.

So, is WCF a true successor to (D) COM or has different goals?

EDIT: I'm talking specifically about distributed applications and remote control - for example, a server can cause a dialog box to start on a workstation, workstations can call methods on the server to send responses, etc. I added 'D' to my name accordingly.

+3
source share
4 answers

I don’t know any official guide that names the successor to DCOM, but .NET has two structures that can replace the use of DCOM. This is WCF and .NET Remoting.

WCF , DCOM .. , .NET 3.0 ; .NET. .NET , . , Remoting DCOM, , .

, WCF , , , WCF. .NET - , , DCOM. , , / .

, , WCF Remoting. -. , - , - http/https. , DCOM.

, WCF, .NET Remoting , DCOM. , COM- DCOM. , , .NET; DCOM - . , , , . DCOM.

+1

WCF COM. .NET - COM.

WCF / , - SOAP, // .

+8

WCF , //. COM/DCOM dot-net . B/c net com .

+2

. WCF COM.

COM:

.Net. . (// ) . ( -, ). , . - ( , COM...). , , , . , . .Net . (RCW, CCW ..).

-1

Source: https://habr.com/ru/post/1721684/

More articles:


All Articles