Re: Sending a fragmented WebSocket message.

On Mon, 18 Sept 2023 at 23:56, Paul Fotheringham wrote: > > I propose > - changing the CURLWS_TEXT thru CURLWS_PING defines to be their actual > numerical 4-bit values > - rename the curl_ws_send's flags argument to opcode > - add an argument to curl_ws_send to replace the CURLWS_OFFSET

Sending a fragmented WebSocket message.

Following on from my post about detecting the final frame of a fragmented WebSocket message there is also an issue sending fragmented messages. I cannot figure out the flags that you are meant to set when calling curl_ws_send with each fragment and I suspect there is no correct combination.

Re: Detecting final frame of a received WebSocket message.

I went ahead and put a PR up for this. On Wed, 13 Sept 2023 at 20:52, Paul Fotheringham wrote: > > Hi, > > I posted back in July asking about how to detect the final frame in a > fragmented WebSocket message because I couldn't see how it was exposed > in the libcurl API. Daniel, you asked some

Detecting final frame of a received WebSocket message.

Hi, I posted back in July asking about how to detect the final frame in a fragmented WebSocket message because I couldn't see how it was exposed in the libcurl API. Daniel, you asked some questions so apologies for the delay. I can confirm that the received frames in my own set-up were all

Re: Getting a list of easy handles in a multi handle - possible?

On Mon, 28 Aug 2023 at 22:32, Daniel Stenberg wrote: > First out, we already deny most libcurl functions from getting called from > their callbacks precisely because of the challenges. > > When libcurl calls a callback it is "in the middle of something", while when > it returns back to the

Re: Getting a list of easy handles in a multi handle - possible?

On Mon, 28 Aug 2023 at 13:34, Daniel Stenberg via curl-library wrote: > > I'm interested to hear others' opinions on prefered API for this functionality > as well. I don't think we need to judge a winner approach just yet. > IMO, I think Brad's suggestion of a dispatch mechanism is far nicer

Re: Detecting final WebSocket frame of a fragmented message

>> On Wed, 12 Jul 2023 at 11:25, Mike Duglas via curl-library >> wrote: >> > >> > Hi, >> > >> > bytesleft == 0 means no more data in this frame. >> > bytesleft == 0 and CURLWS_CONT bit is not set means the end of the message. >> > >> > -- >> > Mike >> >> Thanks for the reply. >> >> Unfortunately

Re: curl-library Digest, Vol 24, Issue 4

On Wed, 12 Jul 2023 at 11:25, Mike Duglas via curl-library wrote: > > Hi, > > bytesleft == 0 means no more data in this frame. > bytesleft == 0 and CURLWS_CONT bit is not set means the end of the message. > > -- > Mike Thanks for the reply. Unfortunately that does not seem to be the case for

Detecting final WebSocket frame of a fragmented message

Hi, I've been using libcurl for some months now and recently tried to get WebSocket going in CURLOPT_CONNECT_ONLY=2L mode. The problem I'm having is if the server sends a message fragmented over multiple frames then I cannot work out how I am meant to know when the final frame of the message is