You are reading a single comment by @samppa and its replies.
Click here to read the full conversation.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
@samppa
@Gordon Faster timeout on client side makes the situation worse since the request that has gone out from client cannot be aborted in a way that it would go away from the buffers on network or sever side. Therefore issuing new request after timeout just adds to the pile. The request can be aborted on the client side ajax but I think that has no effect on server side.
Of course after timeout I could wait longer before issuing next request, but that is handled kind of automatically by waiting the timeout longer.
Using WebSockets is a bit more complicated (not done that before and I like the idea of stateless and client agnostic server) so I would not like to go there now that the requests actually work :-)
How should I close and reopen the server in a sound way (code example)?
By the way, thank you so much for helping me out!