fix set/getSocketOption inheritance #7480
Merged
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.
This is an exact replacement for #7270
Description of Change
int WiFiClient::fd() const
tovirtual int WiFiClient::fd() const
int WiFiClientSecure::fd() const
setSocketOption
,getSocketOption
fromWiFiClientSecure
to deduplicate the code.setSocketOption
,getSocketOption
,getOption
, andsetOption
inWiFiClient
operate onfd()
. With this fix they all operate on the correct socket.setNoDelay
andgetNoDelay
now also works forWiFiClientSecure
.Tests scenarios
tested using WiFiclientSecure and WiFiClient on esp32devkit v1, connected and setNoDelay.
Tested using the MQTT client as referenced to in the issue #7244
Related links
Closes #7244