Chun-Chieh Li 89e2406ab2 ESP8266: Simplify flow control and enable per-socket reconnection ... 1. Fix 'spurious close' by adding close() in open(). 'spurious close' gets frequent and cannot ignore when send() changes to asynchronous. User can retry open() until 'spurious close' gets true. 2. Allow only one actively sending socket because: (1) ESP8266 AT packets 'SEND OK'/'SEND FAIL' are not associated with socket ID. No way to tell them. (2) In original implementation, ESP8266::send() is synchronous, which implies only one actively sending socket. 3. Register 'SEND OK'/'SEND FAIL' oobs, like others in ESP8266::ESP8266 constructor. Don't get involved in oob management with send status because ESP8266 modem possibly doesn't reply these packets on error case. 4. Now that ESP8266::send() changes to asynchronous, drop the code with _parser.recv("SEND OK")/_parser.recv("SEND FAIL"). _parser.recv("SEND OK")/_parser.recv("SEND FAIL") and 'SEND OK'/'SEND FAIL' oobs both consume 'SEND OK'/'SEND FAIL' packets and complicate flow control.		2020-06-19 17:54:34 +08:00
..
ESP8266.cpp	ESP8266: Simplify flow control and enable per-socket reconnection	2020-06-19 17:54:34 +08:00
ESP8266.h	ESP8266: Simplify flow control and enable per-socket reconnection	2020-06-19 17:54:34 +08:00