Approaches of interprocess communication
Nikita the Spider
NikitaTheSpider at gmail.com
Fri Feb 16 15:48:17 EST 2007
More information about the Python-list mailing list
Fri Feb 16 15:48:17 EST 2007
- Previous message (by thread): Approaches of interprocess communication
- Next message (by thread): Approaches of interprocess communication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
In article <1171620696.577982.283740 at m58g2000cwm.googlegroups.com>, "exhuma.twn" <exhuma at gmail.com> wrote: > Hi all, > > Supposing you have two separate processes running on the same box, > what approach would you suggest to communicate between those two > processes. Hi exhuma, That would depend on what data I was exchanging between the processes. For instance, if process A spawns work process B and wants to be able monitor B's progress, a message-based protocol might be kind of chatty. In this situation shared memory is probably a better fit because B can write it's progress to a chunk of shared memory and A can read that at its leisure. OTOH if the conversation is more event-driven, then a messaging protocol makes good sense. FYI there's a Python module (with sample code) for using shared memory on most *nix systems here: http://NikitaTheSpider.com/python/shm/ HTH -- Philip http://NikitaTheSpider.com/ Whole-site HTML validation, link checking and more
- Previous message (by thread): Approaches of interprocess communication
- Next message (by thread): Approaches of interprocess communication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list