Hi Daniel,
From a brief look at the document, it looks like Curl will provide only
WebSocket frame level of communication, so the client will have to implement
full message assembling itself.
Summarizing this approach, it seems that libcurl will provide the following:
1. WS handshake handling
> On Aug 11, 2021, at 6:34 PM, Daniel Stenberg wrote:
>
> On Wed, 11 Aug 2021, Felipe Gasper wrote:
>
>> Why frame by frame? JS’s API only does full messages, and I think the RFC
>> actually stipulates that.
>
> When a single frame can be 61 bits large?
I believe most implementations
> On Aug 11, 2021, at 17:46, Daniel Stenberg via curl-library
> wrote:
>
> A single fragment can be 61 bits large and a message consists of multiple
> such fragments: we must have an API that provides data piece by piece to the
> applicaiton and signal the FIN when it arrives.
Why frame by
On Wed, 11 Aug 2021, Felipe Gasper wrote:
Why frame by frame? JS’s API only does full messages, and I think the RFC
actually stipulates that.
When a single frame can be 61 bits large?
--
/ daniel.haxx.se
| Commercial curl support up to 24x7 is available!
| Private help, bug fixes,
Hi,
I've refreshed the wiki page a bit using input from the discussion so far. See
https://github.com/curl/curl/wiki/WebSockets
A few things I realized and tried to reflect in the page:
A single fragment can be 61 bits large and a message consists of multiple such
fragments: we must have an
