Re: [hybi] Message Strategy. Was: Connection Strategy

[Martin Tyler <martin.tyler at boo.org>]

Sorry for not quoting, it's getting a bit out of order :)

The multiplexing stuff.. I made a comment a few days ago which I don't think was responded to...

Carrying multiple 'channels' over one socket to maybe allow multiple client widgets talking to the same server to use the same socket means more complexity on the server side. Without some kind of common server API for people to write to this would be prohibitive to people writing simple WebSocket servers as described a few weeks ago (12 year olds)

The use case mentioned, a number of widgets on a single page... if they are talking to the same server I would think it is likely that they can use a client side api to manage the multiplexing. If the widgets are truly totally separate pieces of software written by different people how likely is it that they will be talking to the same server?

Maybe we should go into more detail on the use case for channels/multiplexing being built in? At the moment I cannot see the scenario where a library on top of websocket couldnt do the job better


Regards
Martin