066681.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
 <HEAD>
   <TITLE> [whatwg] Thread to run Web Socket feedback from the protocol ?
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20Thread%20to%20run%20Web%20Socket%20feedback%20from%20the%20protocol%20%3F&In-Reply-To=%3C95E3D00E-40E0-40C3-AC49-B2F3E3D8154D%40webkit.org%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="066680.html">
   <LINK REL="Next"  HREF="066682.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[whatwg] Thread to run Web Socket feedback from the protocol ?</H1>
<!--htdig_noindex-->
    <B>Alexey Proskuryakov</B> 
    <A HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20Thread%20to%20run%20Web%20Socket%20feedback%20from%20the%20protocol%20%3F&In-Reply-To=%3C95E3D00E-40E0-40C3-AC49-B2F3E3D8154D%40webkit.org%3E"
       TITLE="[whatwg] Thread to run Web Socket feedback from the protocol ?">ap at webkit.org
       </A><BR>
    <I>Wed Dec  9 10:23:08 PST 2009</I>
    <P><UL>
        <LI>Previous message: <A HREF="066680.html">[whatwg] Thread to run Web Socket feedback from the protocol ?
</A></li>
        <LI>Next message: <A HREF="066682.html">[whatwg] Thread to run Web Socket feedback from the protocol ?
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#66681">[ date ]</a>
              <a href="thread.html#66681">[ thread ]</a>
              <a href="subject.html#66681">[ subject ]</a>
              <a href="author.html#66681">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--/htdig_noindex-->
<!--beginarticle-->
<PRE>
On 09.12.2009, at 10:07, Ian Hickson wrote:

&gt;&gt;&gt; I'm absolutely fine with changing WebSocket to change readyState as
&gt;&gt;&gt; part of the same task that dispatches the event
&gt;&gt;
&gt;&gt; Yes, that is what I think the spec should say.
&gt;
&gt; Done.

With the updated text, there is a race condition between closing a 
socket and removing all data that was received. The spec says &quot;When a 
user agent is to close the Web Socket connection, it must drop all 
subsequent data from the server&quot; - but with the current spec text, you 
can get message events after you call close() from onopen handler.

- WBR, Alexey Proskuryakov

</PRE>

<!--endarticle-->
<!--htdig_noindex-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="066680.html">[whatwg] Thread to run Web Socket feedback from the protocol ?
</A></li>
	<LI>Next message: <A HREF="066682.html">[whatwg] Thread to run Web Socket feedback from the protocol ?
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#66681">[ date ]</a>
              <a href="thread.html#66681">[ thread ]</a>
              <a href="subject.html#66681">[ subject ]</a>
              <a href="author.html#66681">[ 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-December/066681.html