Thingspeak – TCP disconnection after channel update
Hello,
When updating the channel feed the TCP connection is terminated by the Thingspeak server immediately after each request (doesn’t matter "bad" or "good").
That behavior does not depend on the method I use (reqests from ESP8266 via WiFi, GPRS, ordinary terminal program under Windows etc.)
Is that normal?
From technical point of view this is not a problem but when using GPRS the service provider charges me for 100kB of data each time the new TCP connection is open (even if seding 100 bytes) so I suspect it would be better (cheaper) to keep the connection open between the reqests.
Thank you in advance for any advice.Hello,
When updating the channel feed the TCP connection is terminated by the Thingspeak server immediately after each request (doesn’t matter "bad" or "good").
That behavior does not depend on the method I use (reqests from ESP8266 via WiFi, GPRS, ordinary terminal program under Windows etc.)
Is that normal?
From technical point of view this is not a problem but when using GPRS the service provider charges me for 100kB of data each time the new TCP connection is open (even if seding 100 bytes) so I suspect it would be better (cheaper) to keep the connection open between the reqests.
Thank you in advance for any advice. Hello,
When updating the channel feed the TCP connection is terminated by the Thingspeak server immediately after each request (doesn’t matter "bad" or "good").
That behavior does not depend on the method I use (reqests from ESP8266 via WiFi, GPRS, ordinary terminal program under Windows etc.)
Is that normal?
From technical point of view this is not a problem but when using GPRS the service provider charges me for 100kB of data each time the new TCP connection is open (even if seding 100 bytes) so I suspect it would be better (cheaper) to keep the connection open between the reqests.
Thank you in advance for any advice. tcp, disconnection MATLAB Answers — New Questions