Re: IPC in C#
- From: Droopy <droopytoonnospam@xxxxxxxxxxx>
- Date: 27 Jan 2006 16:18:39 GMT
Sorry, I didn't get your last sentence.
I mean IPC as an inter process messages queueing mechanism.
3 C# processes send messages concurrently in a queue.
The routing application read messages one by one, route it to appropriate
host.
Answer messages use the same mechanism (in another queue ?)
"Arkady Frenkel" <arkadyf@xxxxxxxxxxxxxxxx> wrote in
news:OB4Lad1IGHA.648@xxxxxxxxxxxxxxxxxxxx:
> 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.
>
>
>
.
- Follow-Ups:
- Re: IPC in C#
- From: Arkady Frenkel
- Re: IPC in C#
- References:
- IPC in C#
- From: Droopy
- Re: IPC in C#
- From: Arkady Frenkel
- IPC in C#
- Prev by Date: Re: rasman api
- Next by Date: Re: IPC in C#
- Previous by thread: Re: IPC in C#
- Next by thread: Re: IPC in C#
- Index(es):
Relevant Pages
|