[whatwg] Feature requests in WebSocket (Was: BWTP for WebSocket transfer protocol)

Jeremy Orlow jorlow at chromium.org
Fri Aug 14 10:16:21 PDT 2009

On Fri, Aug 14, 2009 at 3:45 AM, Ian Hickson <ian at hixie.ch> wrote:

> On Fri, 7 Aug 2009, Jonas Sicking wrote:
> >
> > I agree that these are very interesting features. Especially connection
> > multiplexing is something that I think is a good idea, for the reasons
> > you've mentioned elsewhere in this thread (multiple widgets on the same
> > page).
> How do you envisage multiplexing working? It's not clear to me what we
> could do that would be easier to handle than just having the script
> manually do the multiplexing at the application layer.

I could say the same thing about redirects and authentication.  I think all
of these features can be worked around , so they shouldn't be in v1, but
they should be the first things considered for v2.

That said....

> What would the API
> look like?

It seems like it could be done transparently to the web developer.  If you
open 2 sockets to the same server, the UA could just open another "channel"
on the same connection.

> What would the wire level look like?

It could be as simple as this: An extra byte or two at the beginning of
every message that says which "channel" is transmitting.  A way to send
control messages, two of which would be used to open and close channels.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090814/524de993/attachment-0002.htm>

More information about the whatwg mailing list