Report Twitter Streaming API disconnects and attempt to reconnect

[cstephen]

Although Twitter's Streaming API connections are designed to remain open indefinitely, there are several reasons a client can be disconnected:

• Twitter server restarts or configuration changes
• Internet problems on the client's side
• A client establishes too many connections using the same Twitter app credentials

See the "Disconnections" section of this page for a more complete list.

Currently, if this module gets disconnected from Twitter's Streaming API, it continues to run like nothing happened except that all hashtag counts show up as 0. This needs to be fixed. This module should:

• Report disconnection errors.
• Attempt to reconnect, report each of these attempts, and indicate how much time was spent in an unconnected state so users are aware of how much data is missing.

[cstephen]

This has been resolved. Results are disabled while the module is in a disconnected state to avoid false 0 results. Support for three new optional callback functions, 'connectingCb,reconnectingCb, andconnectedCb`, has been added to allow applications to react to connect/disconnect events in any way.