@Kolban, are you talking from A) an application - or B) firm/middle ware point of view? I assume the latter, because the callback given to the http (request) is a complete response - and I perceive that callback as the "bracket" callback you are talking about. Whether the 'connection' and with it the socket has to be closed right away or later, is that not defined somewhere else? ...version of the http protocol first, and then seccond with timeout?
Cuttrnyly I'm 'walking' through the AT and ESP8266_0v25-wifi modules to have a better undertanding how things work. NetworkJS and http modules are obviously built-in boudles and source cannot be found under http://www.espruino.com/modules/.
Have to find out how built in-code is pulled and where the source of it resides... Do you know?
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.
@Kolban, are you talking from A) an application - or B) firm/middle ware point of view? I assume the latter, because the callback given to the http (request) is a complete response - and I perceive that callback as the "bracket" callback you are talking about. Whether the 'connection' and with it the socket has to be closed right away or later, is that not defined somewhere else? ...version of the http protocol first, and then seccond with timeout?
Cuttrnyly I'm 'walking' through the AT and ESP8266_0v25-wifi modules to have a better undertanding how things work. NetworkJS and http modules are obviously built-in boudles and source cannot be found under http://www.espruino.com/modules/.
Have to find out how built in-code is pulled and where the source of it resides... Do you know?