ESP8266 Developer Zone

Re: Poor function name: espconn_regist_time

2015-12-24T14:10:36+08:00

Hi,

Sorry that espconn_regist_time only works in TCP server mode.

Maybe you could set a timer to check if ESP8266 received any data, and if not till time out, call espconn_disconnect to disconnect it.

Statistics: Posted by ESP_Faye — Thu Dec 24, 2015 2:10 pm

Re: Poor function name: espconn_regist_time

2015-12-23T12:15:42+08:00

I'm looking for the function to set the timeout interval for tcp client connection. But sdk manual says it is for tcp server only. Dose it work with tcp client?

Statistics: Posted by jinhucn — Wed Dec 23, 2015 12:15 pm

Re: Poor function name: espconn_regist_time

2015-08-11T04:59:17+08:00

I agree, naming the functions properly could help a lot!

Statistics: Posted by Veeda — Tue Aug 11, 2015 4:59 am

Poor function name: espconn_regist_time

2015-08-11T00:36:44+08:00

I was studying the function called "espconn_regist_time" and believe that to be a poor function name. Its purpose is to define the timeout interval for a TCP connection.

A possible alternative might be "espconn_regist_timeout" but better yet would be "espconn_set_tcp_timeout".

On a broader note ... maybe we can find a way to review ALL the exposed SDK methods and see if their naming could be improved?

Neil

Statistics: Posted by kolban — Tue Aug 11, 2015 12:36 am