Are the disconnects really the result of
network drops? I recently "discovered" the Features and
Parameters tabs in the V2 app (I'm still new at this)
and notice that the server disconnects after some number
of records have been sent. The server reconnects about
30 seconds later, but neither tab ever completes. Seems
like there is an error along the way that kills the
connection. 100% repeatable.
On January 28, 2018 10:13:40 AM
PST, Stephen Casner <
casner@acm.org> wrote:
I handled wifi shutdowns cleanly when I first implemented telnet and
ssh as their own tasks. Now that they are under Mongoose, it is out
of my control. The socket is owned by the Mongoose code.
-- Steve
On Sun, 28 Jan 2018, Michael Balzer wrote:
I've begun working on the webserver and noticed something that may
be correlated to this: sockets don't get closed when losing the
connection. The effect is visible on both web and telnet server (ssh
not tested). To reproduce, switch the Wifi network with an open
connection, the port will not be available until timeout.
Regards,
Michael