Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #99288
| From | Dennis Lee Bieber <wlfraed@ix.netcom.com> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: Bi-directional sub-process communication |
| Date | 2015-11-23 19:05 -0500 |
| Organization | IISS Elusive Unicorn |
| Message-ID | <mailman.81.1448323558.2291.python-list@python.org> (permalink) |
| References | <B819AD72-C0F9-4E6C-992A-5E5556979883@ravnalaska.net> |
On Mon, 23 Nov 2015 08:54:38 -0900, Israel Brewster <israel@ravnalaska.net>
declaimed the following:
>Concern: Since the master process is multi-threaded, it seems likely enough that multiple threads on the master side would make requests at the same time. I understand that the Queue class has locks that make
Multiple "master" threads, to me, means you do NOT have a "master
process".
Let there be a Queue for EVERY LISTENER.
Send the Queue as part of the request packet.
Let the subthread reply to the queue that was provided via the packet
Voila! No intermixing of "master/slave" interaction; each slave only
replies to the master that sent it a command; each master only receives
replies from slaves it has commanded. Slaves can still be shared, as they
are given the information of which master they need to speak with.
--
Wulfraed Dennis Lee Bieber AF6VN
wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Bi-directional sub-process communication Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2015-11-23 19:05 -0500
csiph-web