Network retry code: Verify behavior and clarify code comments and log messages.

[tfabris]

The code which detects that the network has gone down and come back up again, and which restarts the YouTube stream if needed, has been tweaked a few times since it was written. Now, instead of the single loop of testing the network itself a few times a minute, it also has a new "inner" loop of testing the stream to see if it's up or not.

To do:

• Revisit the code to make sure it's doing what you intend. If the network goes down (as opposed to the stream itself failing) it should make sure to bounce the stream right away when the network comes back up, instead of sitting in the inner loop rechecking the stream.
• Make sure the hysteresis on the inner stream checking loop is correct and that it doesn't wait too long or overflood the log with too many messages.
• Have another pass through the code comments to make sure they clearly describe how the inner and outer loops work.
• Reword the log messages to be clear about which loop (inner or outer) is the one that's delivering the message to the log, and what the expected behavior really is.

[tfabris]

This issue may be the root cause of issue #9 :

• Revisit the code to make sure it's doing what you intend. If the network goes down (as opposed to the stream itself failing) it should make sure to bounce the stream right away when the network comes back up, instead of sitting in the inner loop rechecking the stream.

[tfabris]

I have checked in a commit which attempts to address issues #8 and #9 . Will test to make sure these are working correctly in production before I close these bugs.

[tfabris]

I'm running these changes on production now so I'm closing this bug.