Client could choose if they want to receive control packets and handle
them.
* If disabled (default) the transport itself tries to handle PING
and CLOSE frames automatically during read operation. If handled
correctly, read outputs 0 indicating no (actual app) data received.
* if enabled, all control frames are passed to the application to be
processed there.
Closes https://github.com/espressif/esp-idf/issues/6307
* Original commit: espressif/esp-idf@acc7bd2ca4
transport_ws can now be read multiple times in a row to read frames larger than the buffer.
Added reporting of total payload length and offset to the user in websocket_client.
Added local example test for long messages.
Closes IDF-1083
* Original commit: espressif/esp-idf@ffeda3003c
esp_netif_init() returns standard esp_err_t error code (unlike tcpip_adapter init), so shall be checked for the return value
Also to make the initialization code more consistent.
* Original commit: espressif/esp-idf@31b2702387
- Added a example test that connects to a local python websocket server.
- Added readme for websocket_client example.
Closes IDF-907
* Original commit: espressif/esp-idf@67c5225c14
