Approaches of interprocess communication
Daniel Nogradi
nogradi at gmail.com
Fri Feb 16 05:54:06 EST 2007
> Supposing you have two separate processes running on the same box,
> what approach would you suggest to communicate between those two
> processes.
>
> Let me list the ones I know of:
>
> * Sockets
> Advantage: Supported per se in nearly every programming language
> without even the need to install additional packages
> Disadvantage: Lot's of code to write, and it's kind of silly to
> communicate via TCP/IP if the processes run on the same machine.
>
> * Webservices
> Advantage: Relatively easy to use, can work across different
> languages
> Disadvantage: Even more overhead on the TCP/IP side that simple
> sockets, as really bulky SOAP messages need to be passed around.
>
> * CORBA -- similar to webservices but more complicated to code.
>
> * Shared memory
> I don't know much about this subject.
>
> Supposing both processes are written in Python, is there any other way
> to achieve this? To me, shared memory sound the most suited approach.
> But as said, I am still fuzzy in this area. Where can I find more
> information on this subject?
Hi, if your requirements are sufficiently light then pylinda might be
an easy-to-use solution:
http://www-users.cs.york.ac.uk/~aw/pylinda/
A simple example is here:
http://www-users.cs.york.ac.uk/~aw/pylinda/beginner.html
HTH,
Daniel
More information about the Python-list
mailing list