Why does a tcp remoting client needs to listen?

Question

When a remoting client creates a TcpClientChannel object, it listens on an (unspecified) port. What for?

A single tcp connection to the server is already a full duplex, so why listen?

Answer 1

I presume it listens for incoming connections. What's full-duplex have to do with it?

Answer 2

I am looking at the MSDN TcpClientChannel Class example and the ServerChannel close by. There is no reference to listening clients. Please elaborate your case.

Another .NET CodeGuru article describes simple remoting and secure remoting.
You can use this to elaborate your point.

Answer 3

The client of the TCP connection has to listen on the source port of the connection, to receive packets transmitted from the server to the client. There are two ports involved in a TCP connection, a source and a destination port. Usually only the destination port is specified, and the source port is just assigned by the OS.