Re: IPC in C#



Socket.BeginReceive/EndReceive and Socket.BeginSend/EndSend internally use
ThreadPool's completion port threads. That is WSASend/WSAReceive API is
used in the overlapped io manner.

So, imo, there is no need to P/Invoke more as there is already P/Invoke when
working with sockets :8-)

Some IPC approaches in .NET ( MMF )
( http://www.codeproject.com/dotnet/globalcache.asp )
(
http://www.dotnetconsult.co.uk/weblog/permalink.aspx/32c3abfb-bac9-4e19-bbc5-39ca338d906d )
--
Vadym Stetsyak aka Vadmyst
http://vadmyst.blogspot.com

"Arkady Frenkel" <arkadyf@xxxxxxxxxxxxxxxx> wrote in message
news:OB4Lad1IGHA.648@xxxxxxxxxxxxxxxxxxxxxxx
> You can use IOCP to reduce number of reading threads ( obviouly though
> PInvoke ).
> Generic method of C# is remoting but that ( as MSMQ btw ) use sockets as
> low layer.
> If you mean IPC in the same maching generic is messaging
> Arkady
>
> "Droopy" <droopytoonnospam@xxxxxxxxxxx> wrote in message
> news:Xns9758A557B3D1Ddroopytoonnospamhotm@xxxxxxxxxxxxxxxxx
>> Hi,
>>
>> I write a routing messages application in C# (framework 1.1).
>> There are 3 other C# applications that are concurrently sending/receiving
>> messages to/from my routing application by using a C# DLL.
>> What is the best way (I mean simple to install and powerful) to implement
>> this ?
>>
>> A first version has been written, using Tcp sockets (1 thread by socket
>> for
>> reading messages) but there are too many sockets => too many threads.
>> Of course, I could improve the ressources usage (using Select or
>> something
>> else to get less threads, multiplexing messages to use less sockets,
>> ...).
>>
>> I would like to use a real and fast IPC.
>> I thought using Memory Mapped File (but I have to PInvoke) or MSMQ (but
>> is
>> it available, I mean is it enable, on all Win XP systems).
>>
>> What IPC are you using ?
>>
>> Thanks in advance.
>
>


.



Relevant Pages

  • Re: Interprocess Communication
    ... The CH2 child will be the controlling process. ... Once control is completed two CH1 children will be communicating in both ... You can do dup/popen etc. but I find sockets simpler with C. ... I thought I would do the additional child using IPC ...
    (comp.os.linux.misc)
  • IPC : Named Pipes, RPC and Sockets etc.
    ... In SQL Server BOL it it is mentioned that Named Pipes, RPC and Sockets ... What are these IPC mechanisms? ...
    (microsoft.public.sqlserver)
  • Re: IPC in C#
    ... I mean IPC as an inter process messages queueing mechanism. ... Answer messages use the same mechanism (in another queue ?) ... >> A first version has been written, using Tcp sockets (1 thread by ...
    (microsoft.public.win32.programmer.networks)
  • Re: IPC in C#
    ... Just simple messages WM_ with Send/PostMessage as basic windows IPC ... Arkady ... > I mean IPC as an inter process messages queueing mechanism. ... >>> A first version has been written, using Tcp sockets (1 thread by ...
    (microsoft.public.win32.programmer.networks)
  • Re: IPC in C#
    ... Arkady ... > when working with sockets:8-) ... >> Generic method of C# is remoting but that (as MSMQ btw) use sockets as ... >>> I would like to use a real and fast IPC. ...
    (microsoft.public.win32.programmer.networks)

Quantcast