- Notifications
You must be signed in to change notification settings - Fork13.3k
TCP: fixes backlog limit handling, and allows ephemeral TCP connections#7096
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
kirillandy commentedFeb 22, 2020 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Hi@d-a-v ! Currently trying to check your changes out, but I'm not too certain about my actions. Is that all I need to do before I compile my code to test out on my ESPs? |
kirillandy commentedFeb 22, 2020
UPDATE: |
devyte left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
LGTM
Jason2866 commentedFeb 23, 2020
Fix#7103 |
Uh oh!
There was an error while loading.Please reload this page.
When a sketch does not check
server::available()often enough, short connections arenow received and stored in background (backlog limit number of connections at most) and can be retrieved and used by subsequentclient = server::available(). Those clients will bestatus() == CLOSED,connected() == falsebutavailable() > 0.@kirillandy Could you check this ? I get what's expected by#2569 with these changes.
@JAndrassy This is still not what you are waiting for but it would be nice if you checked nothing has changed on the arduino side (
WiFiClient::operator bool()has changed).fixes#2569
edit:
fixes#7103