HttpClientChannel Class in VB.NET

Maker QR in VB.NET HttpClientChannel Class

While the HttpChannel class implements both the sending and receiving part of a channel, the HttpClientChannel class only implements the client-side part of the channel. By default, all messages are passed through the SOAP formatter, which means that messages are transmitted via SOAP/XML to the server. Usage example: HttpClientChannel channel = new HttpClientChannel("My Client Channel", null); ChannelServices.RegisterChannel(channel); Configuration example: <configuration> <system.runtime.remoting> <channelSinkProviders> <channel type="System.Runtime.Remoting.Channels.Http.HttpChannel, System.Runtime.Remoting" id="httpbinary" > <clientProviders> <formatter type="System.Runtime.Remoting.Channels. BinaryClientFormatterSinkProvider, System.Runtime.Remoting" /> </clientProviders> </channel> </channels> <application> <channels> <channel ref="httpbinary" /> </channels> <client>

<wellknown url="http://localhost:80/MyRemoteObject.rem" type="MyNamespace.MyRemoteObject, SharedAssembly" /> </client> </application> </system.runtime.remoting> </configuration> The preceding configuration example demonstrates how the HTTP channel can be used with the binary formatter on the client side. On the server side, the same configuration would be used with the <serverProviders> element instead of the <clientProviders> element. More information on MSDN: http://msdn.microsoft.com/library/en-us/cpref/html/ frlrfsystemruntimeremotingchannelshttphttpclientchannelclasstopic.asp

While the HttpChannel class implements both the client and server part, this channel only implements the server-side part of the channel. By default, the channel accepts messages in both SOAP and binary format. Configuration and usage is very similar to the HttpClientChannel. In configuration files, you use the <serverProviders> element instead of <clientProviders>. More information on MSDN: http://msdn.microsoft.com/library/en-us/cpref/html/ frlrfsystemruntimeremotingchannelshttphttpserverchannelclasstopic.asp

This namespace includes client- and server-side channels for interactions via a proprietary TCP-based protocol.

As with the HttpChannel class, the TcpChannel class implements both the client- and the server-channel part for transmitting messages across the wire using the TCP protocol. Therefore, it is a combination of the TcpClientChannel as well as the TcpServerChannel. By default, it accepts and transmits messages in binary format. Usage example: TcpChannel channel = new TcpChannel(4711); ChannelServices.RegisterChannel(channel); Configuration example: <configuration> <system.runtime.remoting> <application> <channels>

<channel ref="tcp" port="1234"> <serverProviders> <formatter ref="binary" /> </serverProviders> </channel> </channels> <service> <wellknown type="Server.ServerImpl, Server" objectUri="MyServer.rem" mode="Singleton" /> </service> </application> </system.runtime.remoting> </configuration> For details about the TcpChannel class and its configuration options, take a closer look at the descriptions in 4. More information on MSDN: http://msdn.microsoft.com/library/en-us/cpref/html/ frlrfsystemruntimeremotingchannelstcptcpchannelclasstopic.asp

While the TcpChannel class implements both the client- and the server-side part of the channel, this implementation can be used on clients only. In configuration files, it is used together with the <clientProviders> part for configuration of the message sinks and formatters of the channel. Usage example: TcpClientChannel channel = new TcpClientChannel("My Tcp Channel", null); ChannelServices.RegisterChannel(channel); Configuration example: <configuration> <system.runtime.remoting> <application name="FirstServer"> <channels> <channel ref="tcp" /> </channels> <client> <wellknown type="General.IRemoteFactory, General" url="tcp://localhost:1234/MyServer.rem" /> </client> </application> </system.runtime.remoting> </configuration>

Configuration is similar to HttpClientChannel as well as TcpChannel in general. Therefore, for details, look at the corresponding sections in this appendix. For further details about channel configuration, take a closer look at 4. More information on MSDN: http://msdn.microsoft.com/library/en-us/cpref/html/ frlrfsystemruntimeremotingchannelstcptcpclientchannelclasstopic.asp

Whereas the TcpClientChannel class implements the client-side channel, this class implements the server-side channel only. By default, it accepts messages in either SOAP or binary format. Configuration and usage is very similar to TcpChannel (and TcpClientChannel) except that you use the <serverProviders> element in the configuration files when configuring formatters and message sinks for this channel. More information on MSDN: http://msdn.microsoft.com/library/en-us/cpref/html/ frlrfsystemruntimeremotingchannelstcptcpserverchannelclasstopic.asp

This namespace includes classes that are used to implement and customize the lease-based lifetime management system.

The ILease interface defines the lifetime lease object that is used by .NET Remoting LifetimeServices. The ILease interface allows you to define the properties that will be used by LifetimeServices for evaluating how long a server-side object will be kept alive. It enables the server object to define several types of timeouts. Based on these timeout values, the lifetime service decides when the server-side object can be destroyed. For configuring the lifetime of a server object, you have to override the InitializeLifetimeService() method of the MarshalByRefObject class. Usage example: public override object InitializeLifetimeService() { Console.WriteLine("MyRemoteObject.InitializeLifetimeService() called"); ILease lease = (ILease)base.InitializeLifetimeService(); if (lease.CurrentState == LeaseState.Initial) { lease.InitialLeaseTime = TimeSpan.FromMilliseconds(10); lease.SponsorshipTimeout = TimeSpan.FromMilliseconds(10); lease.RenewOnCallTime = TimeSpan.FromMilliseconds(10); } return lease; }