Logging during Fetching from URLs should provide better sense of GETs themselves (not status pings)

[GoogleCodeExporter]

General logging needs to be improved a bit more during Fetches to help folks 
deduce problems when connections drop, or timeouts occur.

A good default perhaps is to start at a timeout of 1 min on a response ? dunno.

Currently the console shows "status pings" every .5 seconds that do not 
coincide with expectations for the Throttle delay timing users choose, such as 
5000ms or whatever.

(already reported to David via chat, and creating new issue so we don't lose 
track of this general logging improvement during fetches)

Original issue reported on code.google.com by thadguidry on 24 Aug 2011 at 9:33

[GoogleCodeExporter]

Original comment by [email protected] on 1 Sep 2011 at 5:07

• Changed state: Accepted
• Added labels: Milestone-2.5

[GoogleCodeExporter]

r2228 removes the .5 second status pings.

Original comment by [email protected] on 1 Sep 2011 at 6:29

[GoogleCodeExporter]

Original comment by [email protected] on 20 Sep 2011 at 9:27

• Added labels: Milestone-Post-2.5
• Removed labels: Milestone-2.5

[GoogleCodeExporter]

Original comment by tfmorris on 18 Sep 2012 at 6:00

• Removed labels: Milestone-Post-2.5