Skip to content

Commit

Permalink
Remove unresolvable references (#406)
Browse files Browse the repository at this point in the history
  • Loading branch information
mdickinson committed Jul 12, 2021
1 parent 8a03b40 commit c209ef3
Showing 1 changed file with 8 additions and 11 deletions.
19 changes: 8 additions & 11 deletions traits_futures/multiprocessing_router.py
Original file line number Diff line number Diff line change
Expand Up @@ -18,18 +18,15 @@
When the router is started (via the ``start`` method), it sets up the
following machinery:
- A process-safe process message queue that's shared between processes
(:attr:`MultiprocessingRouter._process_message_queue`). This queue runs in
its own manager server process (the manager is
- A process-safe process message queue that's shared between processes. This
queue runs in its own manager server process (the manager is
:attr:`MultiprocessingRouter.manager`), and the main process and worker
processes use proxy objects to communicate with the queue.
- A thread-safe local message queue
(:attr:`MultiprocessingRouter._local_message_queue`) in the main process.
- A long-running thread (:attr:`MultiprocessingRouter._monitor_thread`),
running in the main process, that continually monitors the process message
queue and immediately transfers any messages that arrive to the local message
queue.
- A :class:`IPingee` instance that's pinged by the monitor thread whenever a
- A thread-safe local message queue in the main process.
- A long-running thread running in the main process, that continually monitors
the process message queue and immediately transfers any messages that arrive
to the local message queue.
- A :class:`~.IPingee` instance that's pinged by the monitor thread whenever a
message is transferred from the process message queue to the local message
queue, alerting the GUI that there's a message to process and route.
Expand All @@ -42,7 +39,7 @@
process message queue) and places the message onto the local message queue.
It also pings the pingee.
- assuming a running event loop, the pingee receives the ping and executes
the :meth:`MultiprocessingRouter._route_message` callback
the ``MultiprocessingRouter._route_message`` callback
- the ``_route_message`` callback pulls the next message from the local message
queue, inspects it to determine which receiver it should be sent to, and
sends it to that receiver
Expand Down

0 comments on commit c209ef3

Please sign in to comment.