021946.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [whatwg] 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%20BWTP%20for%20WebSocket%20transfer%20protocol&In-Reply-To=%3C4A82A187.4090200%40mortbay.com%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="021941.html">
   <LINK REL="Next"  HREF="021943.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[whatwg] BWTP for WebSocket transfer protocol</H1>
<!--htdig_noindex-->
    <B>Greg Wilkins</B> 
    <A HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20BWTP%20for%20WebSocket%20transfer%20protocol&In-Reply-To=%3C4A82A187.4090200%40mortbay.com%3E"
       TITLE="[whatwg] BWTP for WebSocket transfer protocol">gregw at mortbay.com
       </A><BR>
    <I>Wed Aug 12 04:03:35 PDT 2009</I>
    <P><UL>
        <LI>Previous message: <A HREF="021941.html">[whatwg] BWTP for WebSocket transfer protocol
</A></li>
        <LI>Next message: <A HREF="021943.html">[whatwg] BWTP for WebSocket transfer protocol
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#21946">[ date ]</a>
              <a href="thread.html#21946">[ thread ]</a>
              <a href="subject.html#21946">[ subject ]</a>
              <a href="author.html#21946">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--/htdig_noindex-->
<!--beginarticle-->
<PRE>Jonas Sicking wrote:

&gt; I'd rather not debate about which process should be used to get to a
&gt; good protocol. I'd rather debate concrete proposals.

Sure.

So I think I'll keep this response short and see if I can
come up with a BWTP mkII  proposal that addresses
the feedback that I've received.

&gt; So, can you describe an application which takes advantage of this
&gt; added value. I.e. an application that transmits JSON, and that would
&gt; not be put at some type of disadvantage (slower, harder to implement,
&gt; impossible to implement etc) if it couldn't use the new 0x01 frame
&gt; type.

An application that sends just a single content type like JSON is
not going to have any advantage from that proposal, because it
can assume that messages will be text/json;charset=utf8 and
be more efficient than anything that actually transmits that.

But any application that might send multiple types and/or charsets
will benefit.   Also any application that might want to conditionally
compress or encrypt a message would benefit.

Also browser that want to share a single connection between multiple
WebSocket API instances would benefit as they could use the metadata
to organize the virtual connections without the need to alter the
payload.

cheers

</PRE>

<!--endarticle-->
<!--htdig_noindex-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="021941.html">[whatwg] BWTP for WebSocket transfer protocol
</A></li>
	<LI>Next message: <A HREF="021943.html">[whatwg] BWTP for WebSocket transfer protocol
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#21946">[ date ]</a>
              <a href="thread.html#21946">[ thread ]</a>
              <a href="subject.html#21946">[ subject ]</a>
              <a href="author.html#21946">[ 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/021946.html