Robert Jordan fa193dc897 2005-11-05 Robert Jordan <[email protected]> 20 jaren geleden
..
ChangeLog fa193dc897 2005-11-05 Robert Jordan <[email protected]> 20 jaren geleden
IpcChannel.cs 9b0fdcef0f 2005-10-16 Robert Jordan <[email protected]> 20 jaren geleden
IpcChannelHelper.cs 811e17d6c0 2005-11-04 Robert Jordan <[email protected]> 20 jaren geleden
IpcClientChannel.cs fa193dc897 2005-11-05 Robert Jordan <[email protected]> 20 jaren geleden
IpcServerChannel.cs fa193dc897 2005-11-05 Robert Jordan <[email protected]> 20 jaren geleden
IpcTransport.cs 9b0fdcef0f 2005-10-16 Robert Jordan <[email protected]> 20 jaren geleden
NamedPipeClient.cs 9b0fdcef0f 2005-10-16 Robert Jordan <[email protected]> 20 jaren geleden
NamedPipeException.cs 9b0fdcef0f 2005-10-16 Robert Jordan <[email protected]> 20 jaren geleden
NamedPipeHelper.cs 9b0fdcef0f 2005-10-16 Robert Jordan <[email protected]> 20 jaren geleden
NamedPipeListener.cs 9b0fdcef0f 2005-10-16 Robert Jordan <[email protected]> 20 jaren geleden
NamedPipeSocket.cs 9b0fdcef0f 2005-10-16 Robert Jordan <[email protected]> 20 jaren geleden
NamedPipeStream.cs 9b0fdcef0f 2005-10-16 Robert Jordan <[email protected]> 20 jaren geleden
README 9b0fdcef0f 2005-10-16 Robert Jordan <[email protected]> 20 jaren geleden

README

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).