Re: [hybi] RFC 6455 WebSockets Frame to Message assembly

You can't interleave websocket messages like that over a single websocket
connection.

You have to finish all the frames for one websocket message before you can
start another websocket message.

--
Joakim Erdfelt <joakim@intalio.com>
webtide.com <http://www.webtide.com/>
Developer advice, services and support
from the Jetty & CometD experts
eclipse.org/jetty - cometd.org

On Fri, Mar 8, 2013 at 5:29 PM, Scott Morgan <scott@adligo.com> wrote:

> Hi Again,
>
>    Again I am sorry if these comments are in the wrong place (email list).
>
> I have been reading;
> http://webtide.intalio.com/2012/10/jetty-9-updated-websocket-api/
>
> I have been wondering how multiple multiple frame messages would share a
> connection and get reassembled.   The specification doen't seem to mention
> this;
> Ie
> Fancy multithreaded Client Sends 2 messages over a single socket;
>     Frame A, part One of 20,000 leagues under the sea
>     Frame B, part One of The Hobbit
>     Frame C, part Two of 20,000 leagues under the sea
>     Frame D, part Two of the Hobbit yea
>
> How should the frames be identified as belonging to the Hobbit?
> I suggest we use the masking key as a id, however I am not sure if it
> would be unique enough.
>
>
> Cheers,
> Scott
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>
>