New Post: Events stop firing

@MartR

Thanks for your response. But please let me clarify to ensure that I understand clearly.

I soak tested for 24 hours. I had logging which logs started and stop events. I also made a note of the time that the start event began and checked it in the stop event. This allowed me to check for short sessions.

You did not intentionally created short sessions, you just listened to the events in order have a good overview of the disconnect.

What I saw in normal use was a startsession event logged, followed 90s later by a stopsession event logged.

Again this was not intentional, you were disconnected from the stream by Twitter?

In some cases though the stopsession fired before the 90 timer had fired which made me conclude that this was something else in the twitter API which was stopping the session early.

Can you have a look 2 messages above, the reply to StfSki. Do you think it might be what you experienced?

The problem I had of course without adding more code to work around that was that the "anti stall" code was actually stalling and remained stalled until the rest of the 90s window expired to restart the session. Not nice. We are throwing away data.

Here I think I got lost, but from what I understand, the code that you created to ensure that your stream was kept alive was causing it to stall.

Final Question

What do you think I could do to improve Tweetinvi and help you with these issues?

Thanks for the help and this detailed answer.