Secure inter process communication through sockets

[ital1]

Hi all

I need to implement an inter process communication on .NET Compact
Framework 1, on a Windows CE.NET 4.1 system.

I think of using sockets in C#.

My question is :

Is it possible to restrict to local only the accesses to my listening
sockets ? (I don't want someone on the network to be able to control my
application from the outside, through my "open" sockets).


Thank you

 

[Daniel Moth]

Yes, e.g. you can check the ip address of the Socket/TcpClient and close it.

However, I suggest you go with P2P queues. Links to them (option 4) and
other options are here:
http://www.danielmoth.com/Blog/2004/09/ipc-with-cf-on-ce-part-1.html

Cheers
Daniel

 

[ital1]

Thank you

Before going further on P2P Queues, I wonder if it's possible (with P2P
Queues) to send the same message to 5 applications that run on the
device, with the "event driven" technique ?

As in Message Queuing (MSMQ), as soon as a msmq message is read then it
is removed from the msmq stack... So I think that P2P Queues would
probably work in the same way ?

 

[ital1]

I've just tested this functionality and it works very well...

The source code from MS helps much !!
(http://msdn.microsoft.com/library/d...tml/point2point_message_queues.asp?frame=true)

And the event-driven style is very cool !

Thank you again.



(e-mail address removed) a écrit :

 

[Paul G. Tobey [eMVP]]

A queue is point-to-point, yes (hence, P2P). However, you could have each
potential client ask for a queue which it provides to be sent messages and
your server could keep a list. That's how NDIS handles notification of
clients when network events happen.

Paul T.