throbber
TcpServerChannel Class
`
`.NET Framework 1.1
`
`Provides an implementation for a server channel that uses the TCP protocol to transmit messages.
`For a list of all members of this type, see TcpServerChannel Members.
`System.Object
`   System.Runtime.Remoting.Channels.Tcp.TcpServerChannel
`
`[Visual Basic]
`Public Class TcpServerChannel
` Implements IChannelReceiver, IChannel
`[C#]
`public class TcpServerChannel : IChannelReceiver, IChannel
`[C++]
`public __gc class TcpServerChannel : public IChannelReceiver,
` IChannel
`[JScript]
`public class TcpServerChannel implements IChannelReceiver, IChannel
`Thread Safety
`Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members
`are not guaranteed to be thread safe.
`Remarks
`By default, the TcpServerChannel will accept either binary or SOAP formatted messages.
`Channels transport messages between applications across remoting boundaries (for example
`application domains, processes, and machines). These crossings include both inbound and outbound.
`The current channel listens on an endpoint for inbound messages. TcpServerChannel converts the
`messages sent along using the TCP protocol from binary format into message objects.
`If there are common language runtimes at both ends of the channel, then a session is created between
`the two ends, in order to connect the client and server sink chains on either side of the boundary
`together. The client part of the channel is located at the end of the client context sink chain. The
`server part of the channel is located at the start of the server context sink chain. Messages are
`delivered to the client channel, travel through it, and are received by an instance of the
`TcpServerChannel. The channel then delivers received and deserialized messages to the first server
`context sink.
`IChannel implementations use channel configuration properties to configure the channel at run time.
`Channel properties can be specified in a configuration file, or programmatically, inside of an
`IDictionary. In a configuration file all values are represented by strings, but when building a property
`IDictionary programmatically, value types can be specified with their native values or with strings.
`The following table shows the channel configuration properties that can be specified for the current
`channel.
`
`McAfee, Inc. Exhibit 1015 Page 1
`
`

`
`Property
`
`name
`
`priority
`
`port
`
`supressChannelData
`
`useIpAddress
`
`rejectRemoteRequests
`
`bindTo
`
`machineName
`
`Description
`
`Indicates the name of the channel. This property
`is used to retrieve a specific channel when
`calling GetChannel. If this property is not set,
`the system defaults to "http". If you want to
`register more than one HttpChannel, each must
`have a unique name. Set this property to the
`Empty string ("") if you want to ignore names,
`but avoid naming collisions. The system will
`allow any number of channels with the
`String.Empty name.
`
`An integer representing the priority assigned to
`this channel. For server channels, the priority
`controls the order in which the channel data
`appears in an ObjRef. Clients will try to connect
`to the server channels in the order that they are
`listed in the ObjRef. The default priority is 1,
`and negative numbers are allowed. The default
`priority is 1, and negative numbers are allowed.
`
`An integer specifying the port on which the
`channel will listen. To request that the remoting
`system choose an open port on your behalf,
`specify port "0" (zero). This will create a
`TcpServerChannel instance to listen for
`requests on the dyamically assigned port. This
`is typically done on the client to make sure that
`a TcpServerChannel is listening for callback
`methods.
`
`true or false. Specifies that the channel will not
`contribute to the ChannelData.
`
`true or false. Specifies whether the channel will
`use the IP address in the publication URL instead
`of the computer name.
`
`true or false. Specifies whether to refuse
`requests originating from other computers.
`Specifying true allows only inter‑ AppDomain
`calls on the local computer.
`
`An IP address resolving to the current computer
`that specifies which NIC to bind the current
`channel to.
`
`A string that specifies the machine name used
`with the current channel. Overrides the
`useIpAddress configuration property and the
`
`McAfee, Inc. Exhibit 1015 Page 2
`
`

`
`exclusiveAddressUse
`
`machine name channel data.
`
`true or false. Specifies whether the channel will
`prevent other applications from reusing the IP
`address/port combination by setting the
`SocketOptionName server socket option to
`SocketOptionName.ExclusiveAddressUse. The
`default is true.
`This property is supported only by the .NET
`Framework version 1.1 on the following
`platforms: Windows NT 4.0 with SP4 or later,
`Windows Millennium Edition, Windows 2000,
`Windows XP Home Edition, Windows XP
`Professional, Windows Server 2003 family.
`This property requires administrator privileges
`on platforms prior to the Windows Server 2003
`family.
`
`Requirements
`Namespace: System.Runtime.Remoting.Channels.Tcp
`Platforms: Windows 98, Windows NT 4.0, Windows Millennium Edition, Windows 2000,
`Windows XP Home Edition, Windows XP Professional, Windows Server 2003 family
`Assembly: System.Runtime.Remoting (in System.Runtime.Remoting.dll)
`See Also
`TcpServerChannel Members | System.Runtime.Remoting.Channels.Tcp Namespace
`
`Syntax based on .NET Framework version 1.1.
`Documentation version 1.1.1.
`Send comments on this topic.
`© Microsoft Corporation. All rights reserved.
`
`© 2015 Microsoft
`
`McAfee, Inc. Exhibit 1015 Page 3
`
`

`
`TcpServerChannel Constructor
`(Int32)
`
`.NET Framework 2.0
`
`Initializes a new instance of the TcpServerChannel class that listens on the specified port.
`Namespace: System.Runtime.Remoting.Channels.Tcp
`Assembly: System.Runtime.Remoting (in system.runtime.remoting.dll)
`Syntax
`
`C#
`
`public TcpServerChannel (

`int port
`)
`
`J#
`
`public TcpServerChannel (

`int port
`)
`
`JScript
`
`public function TcpServerChannel (

`port : int
`)
`
`Parameters
`port
`
`The port on which the channel listens.
`
`Remarks
`To request that an available port be dynamically assigned, set the port parameter to 0 (zero).
`
`McAfee, Inc. Exhibit 1015 Page 4
`
`

`
`Example
`The following code example shows the use of this constructor.
`
`C#
`
`// Set up a server channel.
`TcpServerChannel serverChannel = new TcpServerChannel(9090);
`ChannelServices.RegisterChannel(serverChannel);    
`
`.NET Framework Security
`Full trust for the immediate caller. This member cannot be used by partially trusted code. For
`more information, see .
`
`Platforms
`Windows 98, Windows 2000 SP4, Windows Millennium Edition, Windows Server 2003,
`Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP SP2, Windows
`XP Starter Edition
`The .NET Framework does not support all versions of every platform. For a list of the supported
`versions, see System Requirements.
`
`Version Information
`.NET Framework
`Supported in: 2.0, 1.1, 1.0
`See Also
`Reference
`TcpServerChannel Class
`TcpServerChannel Members
`System.Runtime.Remoting.Channels.Tcp Namespace
`
`Community Additions
`
`McAfee, Inc. Exhibit 1015 Page 5
`
`

`
`© 2015 Microsoft
`
`McAfee, Inc. Exhibit 1015 Page 6

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket