python_pinger.git

@@ -8,7 +8,9 @@ repeatedly ping multiple hosts to see if the network is up.

 This is the most naive implementation. For each ping host, the main

 process thread pings them one at a time, and prints any changes.

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

+![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.

 ### Upsides

@@ -24,9 +26,9 @@ affect detecting a problem at another host.

 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.

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

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

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

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

 ### Upsides

@@ -34,13 +36,18 @@ Multi-threaded ping calls won't block each other.

 ### Downsides

-The ping tasks read from, and write to a shared dictionary. (Reading and updating the last status.)

+The ping tasks read from, and write to a shared dictionary. (Reading and

+updating the last status.)

 ## Short Lived Workers

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

+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.

+

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

-[short\_lived\_workers.py](http://git.dlma.com/python_pinger.git/blob/master/short_lived_workers.py)

+See the source: **[short\_lived\_workers.py](http://git.dlma.com/python_pinger.git/blob/master/short_lived_workers.py)**

 ### Upsides

@@ -52,9 +59,13 @@ The ping tasks still read from, and write to a shared dictionary. (Reading and u

 ## Long Lived Looping Workers

-![Long Lived Looping Workers](http://git.dlma.com/python_pinger.git/blob/master/images/ping_long_lived_looping_workers.png)

+I saved the best for last. The only thing the main thread does is bring the

+workers and the print manager to life. The workers each independently do their own loop:

+ping, compare, print, and wait.

+

+![Long Lived Looping Workers](http://dlma.com/images/python_pinger/ping_long_lived_looping_workers.png)

-[long\_lived\_looping\_workers.py](http://git.dlma.com/python_pinger.git/blob/master/long_lived_looping_workers.py)

+See the source: **[long\_lived\_looping\_workers.py](http://git.dlma.com/python_pinger.git/blob/master/long_lived_looping_workers.py)**

 ### Upsides