Process intercommunication

Cliff Wells logiplexsoftware at earthlink.net
Mon Nov 5 13:52:18 EST 2001


On Monday 05 November 2001 02:06, Mikael Olofsson wrote:
> Process A is supposed to be running all the time, while process B will
> only live for a short period of time. Both processes are supposed to
> live on the same machine. After collecting some data, B needs to
> communicate that data to A and A is supposed to acknowledge to B that
> the received data is OK. B is therefore supposed to identify A, and set
> up a two-way communication link to A (with A's help, I suppose). After
> the necessary comunication has taken place, the communication link is
> supposed to be shut down, and B will soon die. B is only supposed to
> know under what name A is running.
>
> Later, A is supposed to be able to repeat the whole thing with a new B.
>
> There may be more than one process (but probably not more than ten)
> knocking on A's door, and A is supposed to deal with them one by one.

Probably the easiest way is to have A listen on a specified network port 
(using select()), and have B connect to that port and pass its data that way.


-- 
Cliff Wells
Software Engineer
Logiplex Corporation (www.logiplex.net)
(503) 978-6726 x308
(800) 735-0555 x308




More information about the Python-list mailing list