Re: [hybi] Multiplexing in WebSocket (Was: HyBi Design Space)

[Julian Reschke <[e-mail]>]

Ian Hickson wrote:
> On Wed, 14 Oct 2009, Julian Reschke wrote:
>> So, for clarity, it would probably be good to state in the draft that 
>> this question was considered not to be an issue.
> 
> I don't think it's not an issue. It's an issue like many others. I'm not 
> going to start listing all the things that were considered in the design 
> of the protocol, that'd just be a massive list of things.

Well, earlier on you said:

> FWIW, so far I've concluded (based on long discussions with a number of 
> developers and implementors) that multiplexing would actually not be that 
> great. It could probably only be used for multiplexing to a single 
> websocket path, without making the handshake highly asymmetric or breaking 
> the HTTP compatibility. If it's intended for per-client multiplexing, it 
> can easily be implemented at the application layer, where a much better 
> job can be done that could be done at the protocol layer. If it's intended 
> for multiclient multiplexing, then it's only helping server load, not 
> client performance, and server load isn't especially an issue here.

So it appears that you aware of that drawback, but chose not to address 
this. I still think it would be helpful to document that.

BR, Julian