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: Daniel Stenberg via curl-library <curl-library_at_cool.haxx.se>
Date: Thu, 12 Aug 2021 08:50:39 +0200 (CEST)
On Wed, 11 Aug 2021, Felipe Gasper wrote:
>> When a single frame can be 61 bits large?
(Of course I meant 63...)
And thanks for this. As you know I'm a WebSockets rookie so I need and
appricate pointers like this!
> I believe most implementations enforce a maximum message length. Mojolicious
> (Perl), for example, stipulates 256 KiB by default.
> (https://metacpan.org/pod/Mojo::Transaction::WebSocket#max_websocket_size) I
> think Firefox is 2 GiB.
It could of course work to have a maximum message size set, but this makes me
curious. Surely a client will run into problems if you use 256KB max size
against a server-side websocket thing that assumes much larger?
Using up to 2 gigabytes buffer for a single message is still several
magnitudes larger than I would want libcurl to do.
Other websockets implementations are doing that then I presume?
Date: Thu, 12 Aug 2021 08:50:39 +0200 (CEST)
On Wed, 11 Aug 2021, Felipe Gasper wrote:
>> When a single frame can be 61 bits large?
(Of course I meant 63...)
And thanks for this. As you know I'm a WebSockets rookie so I need and
appricate pointers like this!
> I believe most implementations enforce a maximum message length. Mojolicious
> (Perl), for example, stipulates 256 KiB by default.
> (https://metacpan.org/pod/Mojo::Transaction::WebSocket#max_websocket_size) I
> think Firefox is 2 GiB.
It could of course work to have a maximum message size set, but this makes me
curious. Surely a client will run into problems if you use 256KB max size
against a server-side websocket thing that assumes much larger?
Using up to 2 gigabytes buffer for a single message is still several
magnitudes larger than I would want libcurl to do.
Other websockets implementations are doing that then I presume?
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://curl.se/support.html ------------------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2021-08-12