/lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-December/066683.html

https://github.com/whatwg/whatwg.org · HTML · 91 lines · 75 code · 9 blank · 7 comment · 0 complexity · 7b1a7d0168000612f788932dcf79d3e8 MD5 · raw file

  1. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
  2. <HTML>
  3. <HEAD>
  4. <TITLE> [whatwg] Thread to run Web Socket feedback from the protocol ?
  5. </TITLE>
  6. <LINK REL="Index" HREF="index.html" >
  7. <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=%3CE4EC4CDC-F53D-4D53-B4DC-145750DF6611%40webkit.org%3E">
  8. <META NAME="robots" CONTENT="index,nofollow">
  9. <style type="text/css">
  10. pre {
  11. white-space: pre-wrap; /* css-2.1, curent FF, Opera, Safari */
  12. }
  13. </style>
  14. <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  15. <LINK REL="Previous" HREF="066682.html">
  16. <LINK REL="Next" HREF="066685.html">
  17. </HEAD>
  18. <BODY BGCOLOR="#ffffff">
  19. <H1>[whatwg] Thread to run Web Socket feedback from the protocol ?</H1>
  20. <!--htdig_noindex-->
  21. <B>Alexey Proskuryakov</B>
  22. <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=%3CE4EC4CDC-F53D-4D53-B4DC-145750DF6611%40webkit.org%3E"
  23. TITLE="[whatwg] Thread to run Web Socket feedback from the protocol ?">ap at webkit.org
  24. </A><BR>
  25. <I>Wed Dec 9 10:44:56 PST 2009</I>
  26. <P><UL>
  27. <LI>Previous message: <A HREF="066682.html">[whatwg] Thread to run Web Socket feedback from the protocol ?
  28. </A></li>
  29. <LI>Next message: <A HREF="066685.html">[whatwg] Thread to run Web Socket feedback from the protocol ?
  30. </A></li>
  31. <LI> <B>Messages sorted by:</B>
  32. <a href="date.html#66683">[ date ]</a>
  33. <a href="thread.html#66683">[ thread ]</a>
  34. <a href="subject.html#66683">[ subject ]</a>
  35. <a href="author.html#66683">[ author ]</a>
  36. </LI>
  37. </UL>
  38. <HR>
  39. <!--/htdig_noindex-->
  40. <!--beginarticle-->
  41. <PRE>
  42. On 09.12.2009, at 10:07, Ian Hickson wrote:
  43. &gt;&gt;&gt;<i> I'm absolutely fine with changing WebSocket to change readyState as
  44. </I>&gt;&gt;&gt;<i> part of the same task that dispatches the event
  45. </I>&gt;&gt;<i>
  46. </I>&gt;&gt;<i> Yes, that is what I think the spec should say.
  47. </I>&gt;<i>
  48. </I>&gt;<i> Done.
  49. </I>
  50. As discussed on IRC, this leaves us with a race condition between
  51. close() and queued messages. The spec says that once close() is
  52. invoked, incoming data should be dropped, but queued tasks to dispatch
  53. message event will still be coming.
  54. This race condition can of course be fixed without much difficulty. It
  55. may be more difficult to similarly rearrange XHR specs.
  56. I find it unfortunate that where the spec says &quot;queue a task&quot;, most
  57. (or all) implementations will perform those actions immediately. This
  58. may be indistinguishable from JavaScript client code, but it will be a
  59. source of confusion for developers.
  60. - WBR, Alexey Proskuryakov
  61. </PRE>
  62. <!--endarticle-->
  63. <!--htdig_noindex-->
  64. <HR>
  65. <P><UL>
  66. <!--threads-->
  67. <LI>Previous message: <A HREF="066682.html">[whatwg] Thread to run Web Socket feedback from the protocol ?
  68. </A></li>
  69. <LI>Next message: <A HREF="066685.html">[whatwg] Thread to run Web Socket feedback from the protocol ?
  70. </A></li>
  71. <LI> <B>Messages sorted by:</B>
  72. <a href="date.html#66683">[ date ]</a>
  73. <a href="thread.html#66683">[ thread ]</a>
  74. <a href="subject.html#66683">[ subject ]</a>
  75. <a href="author.html#66683">[ author ]</a>
  76. </LI>
  77. </UL>
  78. <hr>
  79. <a href="http://lists.whatwg.org/listinfo.cgi/whatwg-whatwg.org">More information about the whatwg
  80. mailing list</a><br>
  81. <!--/htdig_noindex-->
  82. </body></html>