{{ message }}
TCP: fixes backlog limit handling, and allows ephemeral TCP connections#7096
Merged
Conversation
|
UPDATE: |
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

When a sketch does not check
server::available()often enough, short connections are now 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