024943.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
 <HEAD>
   <TITLE> [whatwg] [hybi] Websocket algorithmic specification
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20%5Bhybi%5D%20Websocket%20algorithmic%20specification&In-Reply-To=%3C4B69F3FB.4000507%40webtide.com%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <style type="text/css">
       pre {
           white-space: pre-wrap;       /* css-2.1, curent FF, Opera, Safari */
           }
   </style>
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="067189.html">
   <LINK REL="Next"  HREF="067196.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[whatwg] [hybi] Websocket algorithmic specification</H1>
<!--htdig_noindex-->
    <B>Greg Wilkins</B> 
    <A HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20%5Bhybi%5D%20Websocket%20algorithmic%20specification&In-Reply-To=%3C4B69F3FB.4000507%40webtide.com%3E"
       TITLE="[whatwg] [hybi] Websocket algorithmic specification">gregw at webtide.com
       </A><BR>
    <I>Wed Feb  3 14:08:59 PST 2010</I>
    <P><UL>
        <LI>Previous message: <A HREF="067189.html">[whatwg] Websocket algorithmic specification
</A></li>
        <LI>Next message: <A HREF="067196.html">[whatwg] Notification API
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#67216">[ date ]</a>
              <a href="thread.html#67216">[ thread ]</a>
              <a href="subject.html#67216">[ subject ]</a>
              <a href="author.html#67216">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--/htdig_noindex-->
<!--beginarticle-->
<PRE>Jamie Lokier wrote:
&gt;<i> Greg Wilkins wrote:
</I>&gt;&gt;<i>  send the following bytes to the remote server
</I>&gt;&gt;<i>  47 45 54 20
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> A literal reading of the spec would interpret that as
</I>&gt;&gt;<i> meaning that the bytes actually have to be sent, while
</I>&gt;&gt;<i> any sane implementation is going to append the bytes to
</I>&gt;&gt;<i> a buffer to be sent/flushed sometime later.
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> Does this mean that ws server could validly reject a
</I>&gt;&gt;<i> handshake as non compliant if these bytes arrived
</I>&gt;&gt;<i> in the same packet as the subsequent bytes?
</I>&gt;<i> 
</I>&gt;<i> No, because TCP does not preserve write boundaries.
</I>

I know that... you know that..... but will the script kiddie
trying his hand at writing his own server know that?

Anyway, I think the point is moot, as Ian has been
adding text to the spec (in imperative voice :) to
specify what &quot;send&quot; means.

cheers

</PRE>

<!--endarticle-->
<!--htdig_noindex-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="067189.html">[whatwg] Websocket algorithmic specification
</A></li>
	<LI>Next message: <A HREF="067196.html">[whatwg] Notification API
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#67216">[ date ]</a>
              <a href="thread.html#67216">[ thread ]</a>
              <a href="subject.html#67216">[ subject ]</a>
              <a href="author.html#67216">[ 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/2010-February/024943.html