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

https://github.com/whatwg/whatwg.org · HTML · 86 lines · 71 code · 8 blank · 7 comment · 0 complexity · 09a17be62e7053a86f6370d6012d8c51 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=%3C98070607-5D02-4AF5-9606-D9C780A1A991%40apple.com%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="066585.html">
  16. <LINK REL="Next" HREF="066596.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=%3C98070607-5D02-4AF5-9606-D9C780A1A991%40apple.com%3E"
  23. TITLE="[whatwg] Thread to run Web Socket feedback from the protocol ?">ap at apple.com
  24. </A><BR>
  25. <I>Thu Dec 3 13:43:10 PST 2009</I>
  26. <P><UL>
  27. <LI>Previous message: <A HREF="066585.html">[whatwg] Thread to run Web Socket feedback from the protocol ?
  28. </A></li>
  29. <LI>Next message: <A HREF="066596.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#66588">[ date ]</a>
  33. <a href="thread.html#66588">[ thread ]</a>
  34. <a href="subject.html#66588">[ subject ]</a>
  35. <a href="author.html#66588">[ author ]</a>
  36. </LI>
  37. </UL>
  38. <HR>
  39. <!--/htdig_noindex-->
  40. <!--beginarticle-->
  41. <PRE>
  42. On 03.12.2009, at 9:50, Alexey Proskuryakov wrote:
  43. &gt;&gt;<i> If server sends back handshake response and a data frame, and close
  44. </I>&gt;&gt;<i> immediately, fast enough to run JavaScript on browser, how
  45. </I>&gt;&gt;<i> readyState should be?
  46. </I>&gt;<i>
  47. </I>&gt;<i> I'd expect it to work in the same way it works for XMLHttpRequest -
  48. </I>&gt;<i> e.g., in an onreadystate handler of XMLHttpRequest, readyState does
  49. </I>&gt;<i> not change due to background processing of incoming data.
  50. </I>
  51. On the other hand, it can't possibly work like XMLHttpRequest - for
  52. whatever reason, the Web Sockets spec says that events are posted
  53. asynchronously. Maybe I'm not the last an only one to get confused by
  54. this difference from XMLHttpRequest events.
  55. In light of this, I think that the test in question is incorrect.
  56. - WBR, Alexey Proskuryakov
  57. </PRE>
  58. <!--endarticle-->
  59. <!--htdig_noindex-->
  60. <HR>
  61. <P><UL>
  62. <!--threads-->
  63. <LI>Previous message: <A HREF="066585.html">[whatwg] Thread to run Web Socket feedback from the protocol ?
  64. </A></li>
  65. <LI>Next message: <A HREF="066596.html">[whatwg] Thread to run Web Socket feedback from the protocol ?
  66. </A></li>
  67. <LI> <B>Messages sorted by:</B>
  68. <a href="date.html#66588">[ date ]</a>
  69. <a href="thread.html#66588">[ thread ]</a>
  70. <a href="subject.html#66588">[ subject ]</a>
  71. <a href="author.html#66588">[ author ]</a>
  72. </LI>
  73. </UL>
  74. <hr>
  75. <a href="http://lists.whatwg.org/listinfo.cgi/whatwg-whatwg.org">More information about the whatwg
  76. mailing list</a><br>
  77. <!--/htdig_noindex-->
  78. </body></html>