Runtime behaviour net.server:listen()
Posted: Mon Oct 19, 2015 5:36 am
Hi,
I have a question to runtime behaviour of the nodemcu.
I would like to transfer some measured values from one device to another. The first device reads the values from sensors and provides the values with a small web server. The second device requests the values from the web server.
The reading of the sensors might take some time and should not be interrupted by an external request. It should be no problem if the response of the web server is a bit delayed.
Maybe my questions are much too detailed: How is net.server:listen() realized? Is it working like an interrupt? Or is this function called after another function has ended?
So maybe the device is inside the sensor reading function can I set a flag to delay the request of the server function?
Similar race conditions might happen if long multiple long timer routines are used. I found no documentation about this.
I have a question to runtime behaviour of the nodemcu.
I would like to transfer some measured values from one device to another. The first device reads the values from sensors and provides the values with a small web server. The second device requests the values from the web server.
The reading of the sensors might take some time and should not be interrupted by an external request. It should be no problem if the response of the web server is a bit delayed.
Maybe my questions are much too detailed: How is net.server:listen() realized? Is it working like an interrupt? Or is this function called after another function has ended?
So maybe the device is inside the sensor reading function can I set a flag to delay the request of the server function?
Similar race conditions might happen if long multiple long timer routines are used. I found no documentation about this.