Re: [boost] [beast] Chunking example

Subject: Re: [boost] [beast] Chunking example
From: Vinnie Falco (vinnie.falco_at_[hidden])
Date: 2017-07-02 16:19:08

On Sun, Jul 2, 2017 at 9:18 AM, Bjorn Reese via Boost
<boost_at_[hidden]> wrote:
> On 07/02/2017 04:44 PM, Vinnie Falco via Boost wrote:
> Chunking is (abstractly speaking) similiar to WebSocket frames, so I
> am surprised at how different these solutions are.

Actually Beast treats them very similarly. Its not generally possible
in Beast to see the WebSocket frame boundaries either (especially if
you have compression on). It might look like you can see frame
boundaries because of the function `websocket::stream::read_frame` but
that function can cross boundaries or return less than a full frame.

As per rfc6455 (WebSocket) interfaces presented to the application
(`beast::websocket::stream` in this case) are free to reframe
messages.