022027.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [whatwg] Feature requests in WebSocket (Was: BWTP for WebSocket transfer protocol)
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20Feature%20requests%20in%20WebSocket%20%28Was%3A%20BWTP%20for%20WebSocket%0A%20transfer%20protocol%29&In-Reply-To=%3CPine.LNX.4.62.0908141035510.6420%40hixie.dreamhostps.com%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="021928.html">
   <LINK REL="Next"  HREF="022049.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[whatwg] Feature requests in WebSocket (Was: BWTP for WebSocket transfer protocol)</H1>
<!--htdig_noindex-->
    <B>Ian Hickson</B> 
    <A HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20Feature%20requests%20in%20WebSocket%20%28Was%3A%20BWTP%20for%20WebSocket%0A%20transfer%20protocol%29&In-Reply-To=%3CPine.LNX.4.62.0908141035510.6420%40hixie.dreamhostps.com%3E"
       TITLE="[whatwg] Feature requests in WebSocket (Was: BWTP for WebSocket transfer protocol)">ian at hixie.ch
       </A><BR>
    <I>Fri Aug 14 03:45:29 PDT 2009</I>
    <P><UL>
        <LI>Previous message: <A HREF="021928.html">[whatwg] BWTP for WebSocket transfer protocol
</A></li>
        <LI>Next message: <A HREF="022049.html">[whatwg] Feature requests in WebSocket (Was: BWTP for WebSocket	transfer protocol)
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#22027">[ date ]</a>
              <a href="thread.html#22027">[ thread ]</a>
              <a href="subject.html#22027">[ subject ]</a>
              <a href="author.html#22027">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--/htdig_noindex-->
<!--beginarticle-->
<PRE>On Fri, 7 Aug 2009, Jonas Sicking wrote:
&gt;<i> 
</I>&gt;<i> I agree that these are very interesting features. Especially connection 
</I>&gt;<i> multiplexing is something that I think is a good idea, for the reasons 
</I>&gt;<i> you've mentioned elsewhere in this thread (multiple widgets on the same 
</I>&gt;<i> page).
</I>
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. What would the API 
look like? What would the wire level look like?

&gt;<i> But even compression is nice if it was possible.
</I>
It's not clear to me that compression would be particularly useful for 
short packets. I agree that it could be useful for bigger packets; maybe 
when we support binary frames we should say that the frames are 
compressed?

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
<A HREF="http://ln.hixie.ch/">http://ln.hixie.ch/</A>       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
</PRE>

<!--endarticle-->
<!--htdig_noindex-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="021928.html">[whatwg] BWTP for WebSocket transfer protocol
</A></li>
	<LI>Next message: <A HREF="022049.html">[whatwg] Feature requests in WebSocket (Was: BWTP for WebSocket	transfer protocol)
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#22027">[ date ]</a>
              <a href="thread.html#22027">[ thread ]</a>
              <a href="subject.html#22027">[ subject ]</a>
              <a href="author.html#22027">[ author ]</a>
         </LI>
       </UL>

<hr>
<a href="http://lists.whatwg.org/listinfo.cgi/whatwg-whatwg.org">More information about the whatwg
mailing list</a><br>
<!--/htdig_noindex-->
</body></html>

/lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-August/022027.html