Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
Once this is done, a client device can connect to the access point of my server and make http requests.
The problem occurs when the client disconnects and reconnects from my access point. After trying "max_sockets" my server gets stuck and does not respond to client requests,
I have noticed that if before the client disconnects from my server, I stop the http port with the function:
wiced_http_server_stop (& ap_http_server);
and then I start again the http port, my server is no longer locked when I disconnect and reconnect to the access point, however this solution is not very useful, since I can not detect when a client is connected to my access point of unless the client makes an http request.
My two questions are:
How can I detect when a client device has just connected to the access point of my server, without having sent a request to the server?
Is there any other way to prevent my server from locking without having to restart my http port?
I think you can have a reference from below method in wwd_wifi.c
wwd_wifi_get_associated_client_list , you can initialize a timer to get the associated client list in your application, and the usage is included in this function. I have tested this function , it can get accurate Mac address associated.
For your second question:
I run the http test based on apsta in snip with chip 43907, sorry i don't have the board of your type in my hand. It has no problem with a 5G AP mode . and the steps are:
1. application start, PC connect to the softAP created.
2. visit the host web address.
3. disconnect the PC connection.
4. reconnected, visit the host address again, and didn't restart the HTTP port.