-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
range over incoming eventually quits #15
Comments
I would expect that to happen when the TCP session is broken for some
reason. Is it possible you are passing through a NAT which times out?
|
Yes, it's quite possible. I'm running this program on a Raspberry Pi in my office and connecting to a mosquitto running in AWS. I'm trying to think of a better strategy for handling errors that may involve putting that range loop in another loop. |
Could we export the Done channel from the client so that my program could be notified that it's shutdown and reconnect? |
I am open to pull requests. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I stole this chunk of code from one of your examples and then added a Println() call:
and saw that if there weren't any messages for some period of time it would exit the for loop and my program would end.
Is this because of something on the mosquitto server closing my connection for being idle?
The text was updated successfully, but these errors were encountered: