[Mono-devel-list] differences between Remoting.Channels.Tcp.TcpChannel on Mono and MS

Patrick McMorris patrick at gwnsoftware.com
Tue Jun 22 16:53:31 EDT 2004

I am using System.Runtime.Remoting.Channels.Tcp.TcpChannel in my
application and I have noticed a couple of differences between the
Microsoft implementation and the Mono implementation. They are...
1. When you create a new instance of the TcpChannel object with a
non-zero port, the Microsoft implementation will automatically start
listening on that port. However the Mono implementation requires
StartListening to be called.
2. On Mono the top of the TcpServerChannel.StartListening function looks
like this;
		public void StartListening (object data)
			listener = new TcpListener (bindAddress, port);
This means that a new listener (object member) will be created each
time, with the result that a second call to the function will cause a
change in state, whereas in the Microsoft implementation calling
StartListening multiple times has no additional effect.

Now I note that the MSDN docs don't make any comment on whether the
constructor for TcpChannel will call StartListening or not.

Question: What is the aim of Mono's implementation of Remoting;
1. To implement the interface defined by the MSDN docs?
2. To implement the as similar functionality as possible?


More information about the Mono-devel-list mailing list