👆 #90 is a(n untested) proposal that might increase the robustness of the streaming classes. It adds options to detect timeout from the stream (ie. if there's no comment or event/data received for too long), and to optionally restart the stream if that occurs (or throw a TimeoutException if not restarting).

What do you think?

I've done some further experimentation, and I'm pretty convinced now the issue I've seen is not in Mastonet after all*.

However, adding a little defensive code around the stream may still be helpful - if, say, it's closed at either end for some unexpected reason it's probably still good to be able to re-open it again.

*I failed to keep a reference to the Task that was running the streaming. I suspect it was silently garbage collected.