Hi Josh,
I am constantly trying to improve the Reconnect part of the Streams.
Though I leave it to the developers to implement their reconnect strategy on their own. Personally I do not have increase delays in my reconnect strategies and I never encountered any issue by doing so.
I cannot implement the reconnect strategy for the developers as each of them might want to handle these differently.
But the idea is simply that when the Stopped event is received you can listen to the event and react based on the information you received.
As per the ExceptionHandler. Tweetinvi is no longer supporting it for Streams at the moment because as I said, you could expect the ExceptionHandler to be the one from the main thread (from which the stream has been created or the one from the actual running thread).
Please let me know if you need more information.
Cheers,
Linvi
I am constantly trying to improve the Reconnect part of the Streams.
Though I leave it to the developers to implement their reconnect strategy on their own. Personally I do not have increase delays in my reconnect strategies and I never encountered any issue by doing so.
I cannot implement the reconnect strategy for the developers as each of them might want to handle these differently.
But the idea is simply that when the Stopped event is received you can listen to the event and react based on the information you received.
As per the ExceptionHandler. Tweetinvi is no longer supporting it for Streams at the moment because as I said, you could expect the ExceptionHandler to be the one from the main thread (from which the stream has been created or the one from the actual running thread).
Please let me know if you need more information.
Cheers,
Linvi