python_pinger.git

@@ -10,7 +10,8 @@ process thread pings them one at a time, and prints any changes.

 ![Single Threaded Pings](http://dlma.com/images/python_pinger/ping_single_threaded.png)

-It's so simple that I'm not going to provide a sample source file, but for the others below, I will.

+It's so simple that I'm not going to provide a sample source file,

+but for the others below, I will.

 ### Upsides

@@ -24,10 +25,13 @@ affect detecting a problem at another host.

 ## Long Lived Workers Consuming from Queue

 Raymond Hettinger's [PyBay 2018 Keynote](https://pybay.com/site_media/slides/raymond2017-keynote/threading.html)

-uses the queue module to send data between threads, so I thought I'd make a version of the pinger that did the same.

+uses the queue module to send data between threads, so I thought I'd make a

+version of the pinger that did the same.

 ![Long Lived Queue Workers](http://dlma.com/images/python_pinger/ping_long_lived_queue_workers.png)

+The main thread sends an address to a queue that the worker threads wait upon.

+

 See the source: **[long\_lived\_worker\_queue.py](http://git.dlma.com/python_pinger.git/blob/master/long_lived_worker_queue.py)**

 ### Upsides

@@ -43,7 +47,8 @@ updating the last status.)

 How about we don't keep the workers around, and only spawn them when

 there's something to do? That way, we won't waste memory when there's

-nothing going on.

+nothing going on. The main thread passes the address to the workers when

+they're constructed.

 ![Short Lived Workers](http://dlma.com/images/python_pinger/ping_short_lived_workers.png)