Re: [hybi] first draft of WS mux extension

["Len Holgate" <[e-mail]>]

John,

This seems nice and clean and pretty easy to implement. 

Have you considered removing the "relaxation" of the fragmented frame rules
from the base protocol (ie the changes that permit the example shown in 7).

I would have thought that if all fragments on mux channels were sent as
complete messages you could include the actual message's fin bit in the
extension data of the mux frame and so not change the base protocol at all.
This would mean that mux could be implemented on existing websocket
implementations without changing the underlying implementation at all. The
layer "above" could deal with all aspects of the muxing.

Len 

> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] On 
> Behalf Of John Tamplin
> Sent: 21 October 2011 23:52
> To: Iñaki Baz Castillo
> Cc: Hybi
> Subject: Re: [hybi] first draft of WS mux extension
> 
> On Fri, Oct 21, 2011 at 6:33 PM, Iñaki Baz Castillo 
> <[e-mail]> wrote:
> 
> 
> 	2011/10/22 Iñaki Baz Castillo <[e-mail]>:
> 	
> 	> I strongly propose to rename it to "mux".
> 	
> 	
> 	I mean right now, without waiting for it to be an approved RFC.
> 
> 
> Until there is feedback that others besides Google are 
> interested in implementing it, it seems presumptuous to take 
> the name "mux".
> 
> 
> I am aware of the article you reference, but since 
> non-private use names have to be registered before use, it 
> isn't clear the alternative is any better.  WS has already 
> shown that you can have early deployments of a work in 
> progress, make breaking changes, and have implementations 
> adapt to the new version fairly quickly. So, I would much 
> rather have some implementations use x-google-mux first and 
> have to change them later after it is standardized, than to 
> use the name "mux" now and then find out we really want a 
> different mux protocol for that name.  There are only a few 
> browsers, so if they all update the servers will have no 
> choice but to update to match.
> 
> -- 
> John A. Tamplin
> Software Engineer (GWT), Google
> 
>