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

["John A. Tamplin" <[e-mail]>]

On Fri, Mar 8, 2013 at 7:29 PM, Scott Morgan <[e-mail]> wrote:

>    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.
>

You would need to add your own message layer above WebSocket, or use the
mux extension which is under development.

-- 
John A. Tamplin