Files
mono/mcs/class/System.Runtime.Remoting/System.Runtime.Remoting.Channels.Ipc.Win32
Robert Jordan c865cdf96d In Test:
2010-05-29  Robert Jordan  <[email protected]>

	* IpcChannelTest.cs: Add test for bug #609381.

In System.Runtime.Remoting.Channels.Ipc.Win32:
2010-05-29  Robert Jordan  <[email protected]>

	* IpcChannelHelper.cs (copy): Take into account that the remoting
	stack is internally using MemoryStreams all over the place.
	Fixes bug #609381 as a side effect.

	* IpcChannel.cs (.ctor): Create an IpcClientChannel as well.


svn path=/trunk/mcs/; revision=158161
2010-05-29 16:37:13 +00:00
..
…
…

System.Runtime.Remoting.Channels.Ipc.Win32
==========================================

*.Ipc.Win32 is a concrete IPC channel implementation for Win32
using named pipes for the transport sink.

Differences to MSFT's implementation:

- the "secure" channel property is not implemented.

- the implementations are not interoperable. Not a big issue,
  because the IPC channel is a local channel.

About the Named Pipe implementation:

My "native" Win32 implementation for MSFT's .NET used I/O completion ports.
I was not able to port them to Mono because some required functionality
was missing (ThreadPool.BindHandle for example).