Connection not "ok" if server does not send anything except keepalive about micropython-iot HOT 3 CLOSED

I just realized that I am probably still using an old version of client.py on my device. In this version self.ok=True was still in line 125 after the self.readline which would be expected to result in the described behavior.
Will get back after testing with the new version but don't expect it to be a problem anymore. Sorry.

from micropython-iot.

Well spotted but I think that's a bug I fixed a few days ago.

I should warn that there is a minor API change in the works. This affects the server side only, namely args to server.run(). Instead the number of connections the function now expects a set containing the client_id's of the expected clients. This enables checks to be made for unexpected or duplicate clients.

It also facilitates a server.wait_all() coro, where a server-side application coro pauses on startup until all expected clients have connected. This is the main reason for the change: in applications where clients communicate with each other, the server-side application needs to "know" that all clients have made initial connections.

The current s_comms_cp.py does this at application level which is clunky. The new version simply waits on the above function before proceeding.

from micropython-iot.

Yeah should have checked my source file on the microcontroller first. With the new version including your fix it is working just fine.

That sounds interesting, thanks for letting me know. Will implement something similar in my server application. I don't use any of your server code by now. My approach however is more dynamic, creating clients as they connect. No need to know which clients will connect.

from micropython-iot.