Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: more WebSockets
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Felipe Gasper via curl-library <curl-library_at_cool.haxx.se>
Date: Wed, 11 Aug 2021 18:32:34 -0400
> On Aug 11, 2021, at 17:46, Daniel Stenberg via curl-library <curl-library_at_cool.haxx.se> 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 frame? JS’s API only does full messages, and I think the RFC actually stipulates that.
-F
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
Received on 2021-08-12
Date: Wed, 11 Aug 2021 18:32:34 -0400
> On Aug 11, 2021, at 17:46, Daniel Stenberg via curl-library <curl-library_at_cool.haxx.se> 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 frame? JS’s API only does full messages, and I think the RFC actually stipulates that.
-F
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
Received on 2021-08-12