* Add function so that the total number of web-socket clients can be limited easily. This is to cope with a problem when a browser does not close the web-socket connection correctly. I have observed this on Chromium based browsers. The memory leak will eventually lead to the server crashing. Normally only one connection per client is required, so limiting the number of connections would not normally cause any problems.
* Prevent an assertion failure when using WebSockets
Frequently when using Web Sockets you will get the assert failure:
assertion "new_rcv_ann_wnd <= 0xffff" failed: file "/Users/ficeto/Desktop/ESP32/ESP32/esp-idf-public/components/lwip/lwip/src/core/tcp.c", line 779, function: tcp_update_rcv_ann_wnd
This will happen particulary when you close the browser window. This change
prevents the issue from occuring.
* Do not use thread locking with the ESP8266, but instead use an empty placeholder class that can be used to implement locking at a later date.
* Do not use thread locking with the ESP8266, but instead use an empty placeholder class that can be used to implement locking at a later date.
* Add function so that the total number of web-socket clients can be limited easily. This is to cope with a problem when a browser does not close the web-socket connection correctly. I have observed this on Chromium based browsers. The memory leak will eventually lead to the server crashing. Normally only one connection per client is required, so limiting the number of connections would not normally cause any problems.
* Set the default number of ws clients dependent on processor.
2f37037029