There are four options for the reference to the coupling.
1.msmq
From Windows NT, Microsoft began to provide MSMQ support, which has been the current 3.0, mainly providing support for several features.
Reliable messaging, similar to the MAIL system, offline support
The priority of the message can be set, and various additional indications of Label
Transaction support
Good scaling through the flexible application of DC, IC
For the client, the requirements must be a Windows system, support from Windowsce to Windows .NET 2003. It can be integrated with other non-Microsoft technology through the connector. Net has a special package System.Messaing Namespace.
2.enterprise Service
In fact, the .NET is actually interacting with the COM application architecture through the hosting Enterprise Service.
From Windows 2000, this component is now available to Windows 2003 version 1.1
I think there are several characteristics worthy of use.
The object pool is particularly suitable for the object constructs, and there is no status. It is very similar to our access to our ADO.NET. Can be combined with JIT.
Distributed transaction coordination, plus transaction compensation. This is a great advantage
Another point is to send coupling events, which is very helpful for Plug and Play's subscription apps.
Of course, the direct client must also be Windows 2000 and OS.
3.DOTNET Remoting
I have the most, I feel the most;)
DOTNET Remoing Chinese translation remote processing, is actually a very good remote processing call under the .NET platform, providing the development of architecture. Flexible communication transfer protocol, of course, you can also expand yourself. The call to the remote object provides a variety of ways, which can be made, or the state can be made. For developers, it feels as convenient to call at all. This is mainly not in Web Service.
In fact, this application is similar to a relatively coupled application. The client and server-wide communication model are based on the .NET platform. In other words, if the client is not necessarily .NET platform, transing is not very suitable. A simple example is the pass of an object
Passing an object from the Remoting server to the client, can be a remote reference to the object, you can also make the copy of an object, which is the MBR or MBV we usually say.
Of course, the web service is a reference to the object, and the web service can only be an MBV, and the MBV here is not complete enough. I'm here
Http://dotnet.mblogger.cn/montaque/posts/2094.aspx refers to the different serialization methods they walk. For web services, just a very shallow COPY. That is to say, when the object is transmitted to the server, there is no 100% of the state.
The object transmitted by Remoting is more authentic. Perhaps this is an embodiment that is more close to the local call relative to the web service.
The shortcomings are mentioned earlier, it is a rich feature based on. Net this platform. .NET in system.Runtime.Remoting.dll
4. Web service.
This is a standard thing, my opinion is that the standard thing is not very good. While ensuring standard, there is a lot of features.
