Approaches of interprocess communication
- From: "exhuma.twn" <exhuma@xxxxxxxxx>
- Date: 16 Feb 2007 02:11:36 -0800
Hi all,
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?
.
- Follow-Ups:
- Re: Approaches of interprocess communication
- From: Hendrik van Rooyen
- Re: Approaches of interprocess communication
- From: Nikita the Spider
- Re: Approaches of interprocess communication
- From: Goldfish
- Re: Approaches of interprocess communication
- From: Bjoern Schliessmann
- Re: Approaches of interprocess communication
- From: Duncan Grisby
- Re: Approaches of interprocess communication
- From: Ben Finney
- Re: Approaches of interprocess communication
- From: Daniel Nogradi
- Re: Approaches of interprocess communication
- From: Gabriel Genellina
- Re: Approaches of interprocess communication
- Prev by Date: Re: I'm faint why this can't work
- Next by Date: Re: KeyboardInterrupt not caught
- Previous by thread: KeyboardInterrupt not caught
- Next by thread: Re: Approaches of interprocess communication
- Index(es):
Relevant Pages
|