Re: [hybi] Is there a traffic jam?

[Greg Wilkins <[e-mail]>]

Ian Hickson wrote:
> Come now. All you have to do to share a connection on the client is have a 
> single object that does all the sending and receiving, with a 
> corresponding piece of code on the server, which simply does three things:

Ian,

implementing multiplexing is not the pain point as there are a million
ways to do it, ranging from trivial to amazingly complex.   We
can multi-plex over HTTP, yet it is still a paint point.

The problem is getting everybody to agree to share and use
the same multiplexing.

Websocket presents a nice simple interface that is easy for web developers
to use directly.  So they will use it directly!    As well as that, there
will be dojo/jquery/prototype/mootools/yahoo/ext/etc wrappers.   The
situation on the server side is even more diverse with regards to servers
and frameworks.

There is ZERO chance that all these diverse communities will come together
and decide on how to share and multiplex connections.   Websockets will
simply encourage direct consumption of connections.  If you are really
lucky, some frameworks might do their own multiplexing between their
own widgets and frames.    But with websocket, it simply will not
happen that a common standard will easily/quickly emerge for sharing and
multiplexing.


regards