Repository navigation
Conversation
When using `curl_ws_send()`, perform a blocking send of the data under the following conditions: - the websocket is in raw mode and the call is done from within a curl callback. A partial write of the data could subsequently mess up the ws framing, as a callback has a hard time handling this. - the websocket is encoding the data itself, has added it to its internal sendbuf. A partial flush of the buffer has unclear semantics for the caller, as they will have no idea what to send again. Fixes WebSockets tests with CURL_DBG_SOCK_WBLOCK=90 set.
Contributor
|
Should this blocking behaviour be documented somewhere along with the other parts of curl that still blocking?
|
Contributor
Author
|
A good question. I did not really like to introduce this, but it seems necessary with the current design. Maybe @bagder has an idea how to address this. But if we go for this, it needs to be documented in |
Contributor
|
There are a number of other blocking calls mentioned in TODO and KNOWN_BUGS. If
this is a temporary measure that might be fixed better in the future, then it
should probably go there, too.
|
Only perform blocking send when invoked by a callback.
Contributor
Author
|
Improved handling to make curl_ws_send() non-blocking in almost all cases when invoked outside a callback. Updated documentation. |
bagder
approved these changes
Aug 12, 2024
|
What is expected of clients who wish to resume a |
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
4 participants
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 using
curl_ws_send(), perform a blocking send of the data if the call is done from within a curl callback. A partial write of the data could subsequently mess up the ws framing, as a callback has a hard time handling waits and repeated calls.Outside a callback,
curl_ws_send()is always non-blocking except when generating a 0-length frame that could not completely be sent. This is no way to report this partial success.Document this behaviour in the function and add this as item to the TODO list. Also, add
wsas protocol trace feature.Fixes WebSockets tests with CURL_DBG_SOCK_WBLOCK=90 set.