On Fri, Aug 14, 2009 at 3:45 AM, Ian Hickson <span dir="ltr"><<a href="mailto:ian@hixie.ch">ian@hixie.ch</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
On Fri, 7 Aug 2009, Jonas Sicking wrote:<br>
><br>
> I agree that these are very interesting features. Especially connection<br>
> multiplexing is something that I think is a good idea, for the reasons<br>
> you've mentioned elsewhere in this thread (multiple widgets on the same<br>
> page).<br>
<br>
How do you envisage multiplexing working? It's not clear to me what we<br>
could do that would be easier to handle than just having the script<br>
manually do the multiplexing at the application layer.</blockquote><div><br></div><div>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.</div>
<div><br></div><div>That said....</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">What would the API<br>
look like?</blockquote><div><br></div><div>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.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">What would the wire level look like?</blockquote><div><br></div><div>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.</div>
</div>