Fix pipelined HTTP client connection on freertos platform #3165
Conversation
This file contains 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
Signed-off-by: stropee <stropee@deltadore.com>
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.
Hi Andy,
I have successfully port an apps from linux platform to a freertos + lwip one.
Everything work like a charm but i only got an issue with a pipelined HTTPS Client connection.
On freertos once established i'm getting WRITEABLE callback but i didn't get the RECEIVE callback.
I have observed that calling lws_service_do_ripe_rxflow like in unix-service.c will generate a POLLIN event and fix the issue.
I didn't get the same issue on a piplined WS Client.
Is this somethings that have been done on other platform and missed on freertos ?
Thanks
Simon