MSMQ, Enterprise Service, DotNet Remoting, Web Servi

There are four options for sending coupling references.
1. MSMQ
Microsoft has been providing msmq support since windows nt, and 3.0 has provided support for several features.
Reliable message transmission, similar to the mail system, with offline support
You can set the priority of a message and various additional labels of a Label.
Transaction support
Flexible application of DC and IC with good scalability
For the client, it must be a windows system, from windowsce to windows. net 2003. You can use the connector to integrate with other non-Microsoft technologies. NET to have a dedicated encapsulation System. Messaing Namespace.
2. Enterprise Service
. NET actually interacts with the COM + application architecture through the hosted Enterprise Service.
This component has been available since windows 2000. Currently, windows 2003 is 1.1.
I think there are several features worth using.
Object pool is especially suitable for applications with slow object construction while stateless. Similar to the connection in ADO. NET. Can be combined with JIT.
Distributed Transaction coordination, coupled with transaction compensation. This is a major advantage
Another point is to send coupling events, which is very helpful for subscription applications of plug and play.
Of course, the direct client must also be windows 2000 or later OS
3. DotNet Remoting
I am using the most, and I feel the deepest ;)
Dotnet remoing remote processing for Chinese translation is actually a good remote processing call under the. NET platform, providing a development architecture. Flexible communication and transmission protocols can also be expanded on your own. Remote Object calls can be stateful or stateless. It is just as convenient for developers to call. This is not applicable to Web Services.
In fact, this application is similar to a relatively coupled application. The rich communication models between the client and the server are based on the. NET platform. That is to say, if the client is not necessarily a. NET platform, remoting is not very suitable. A simple example is object transfer.
Passing an object from the remoting server to the client can be a remote reference of the object, or a copy of the object, which is generally referred to as mbr or mbv.
Of course, the web service cannot implement object reference transfer, and the web service can only be one mbv, while the mbv in the web service is not complete enough. I mentioned in the http://dotnet.mblogger.cn/montaque/posts/2094.aspx that they are going through different serialization methods. For web services, it is just a very simple copy. That is to say, when the object is passed to the server, the 100% status is not passed.