By releasing .Net 2.0 remoting was integrated into the .Net Framework.
Remotnig is a simple technology for communicate between applications across application domains. By using remoting, objects an messages are transported via Channels from a Remotingserver to one or many Remotingclients.
You can select between three different channel types.
Remote Channel Types
TCP
By using a tcp channel dataobjects and messages are transported through a tcp channel. Per default all objects and messages are transformed into a binary stream by using a BinaryFormatter. In a closed network (LAN), tcp is the fastest way to transport data.
HTTP
When you use a HTTP channel, objects and messages are translated into a SOAP message and transported. HTTP should not be used on the Internet.
ICP
ICP (Interprocess communication) can only be used, if both, client and server are located on one machine. ICP manages all security stuff with ACL's. Another limitation is that client and server must be written on the .Net Framework.
Each time you setup remoting you must consider which channeltype is best for the current situation.
Remoting Objects
Type requirements
Each object can be a remoting object, the only thing you have to do is to inherit from MarshalByRefObject.
After adding the base class your type is ready for remoting.
Remoting Applications Types
Each remoting application has two sub-application types:
- Remoting Server Application
- Remoting Client Application
At first I will explain some things about the remoting server application.
Remoting Server Applications
You can choose between four types for hosting a remoting server within a .Net Application:
- .Net Console Application
- .Net Executable
- ASP.Net Application
- .Net Windows Service
Technorati-Tags:
.Net,
Remoting