/lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-April/068380.html

https://github.com/whatwg/whatwg.org · HTML · 113 lines · 89 code · 17 blank · 7 comment · 0 complexity · aafc3d8e6231753e4d08032e4c1630df MD5 · raw file 

    

  1. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
    2. 

  2. <HTML>
    3. 

  3.  <HEAD>
    4. 

  4.    <TITLE> [whatwg] WebSocket closing handshake
    5. 

  5.    </TITLE>
    6. 

  6.    <LINK REL="Index" HREF="index.html" >
    7. 

  7.    <LINK REL="made" HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20WebSocket%20closing%20handshake&In-Reply-To=%3Cop.vby5a7vlidj3kv%40simon-pieterss-macbook.local%3E">
    8. 

  8.    <META NAME="robots" CONTENT="index,nofollow">
    9. 

  9.    <style type="text/css">
    10. 

  10.        pre {
    11. 

  11.            white-space: pre-wrap;       /* css-2.1, curent FF, Opera, Safari */
    12. 

  12.            }
    13. 

  13.    </style>
    14. 

  14.    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
    15. 

  15.    <LINK REL="Previous"  HREF="068378.html">
    16. 

  16.    <LINK REL="Next"  HREF="068383.html">
    17. 

  17.  </HEAD>
    18. 

  18.  <BODY BGCOLOR="#ffffff">
    19. 

  19.    <H1>[whatwg] WebSocket closing handshake</H1>
    20. 

  20. <!--htdig_noindex-->
    21. 

  21.     <B>Simon Pieters</B> 
    22. 

  22.     <A HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20WebSocket%20closing%20handshake&In-Reply-To=%3Cop.vby5a7vlidj3kv%40simon-pieterss-macbook.local%3E"
    23. 

  23.        TITLE="[whatwg] WebSocket closing handshake">simonp at opera.com
    24. 

  24.        </A><BR>
    25. 

  25.     <I>Fri Apr 30 05:07:45 PDT 2010</I>
    26. 

  26.     <P><UL>
    27. 

  27.         <LI>Previous message: <A HREF="068378.html">[whatwg] Should default styles for h1-h6 match the outlining algorithm?
    28. 

  28. </A></li>
    29. 

  29.         <LI>Next message: <A HREF="068383.html">[whatwg] The real issue with HTML5's sectioning model (was:	&quot;Headings and sections,	role of H2-H6&quot; and &quot;Should default styles for h1-h6 match the	outlining algorithm?&quot;)
    30. 

  30. </A></li>
    31. 

  31.          <LI> <B>Messages sorted by:</B> 
    32. 

  32.               <a href="date.html#68380">[ date ]</a>
    33. 

  33.               <a href="thread.html#68380">[ thread ]</a>
    34. 

  34.               <a href="subject.html#68380">[ subject ]</a>
    35. 

  35.               <a href="author.html#68380">[ author ]</a>
    36. 

  36.          </LI>
    37. 

  37.        </UL>
    38. 

  38.     <HR>  
    39. 

  39. <!--/htdig_noindex-->
    40. 

  40. <!--beginarticle-->
    41. 

  41. <PRE>start the WebSocket closing handshake:
    42. 

  42. 

  43. [[
    44. 

  44. Note: The closing handshake finishes once the server returns the 0xFF  
    45. 

  45. packet, as described above.
    46. 

  46. ]]
    47. 

  47. 

  48. I assume it should say 0xFF frame, not packet.
    49. 

  49. 

  50. This note is only true when the client sends the closing handshake first.
    51. 

  51. 

  52. ...except that I can't find anywhere in the server part to send 0xFF 0x00  
    53. 

  53. when it receives 0xFF 0x00 from the client. I just see:
    54. 

  54. 

  55. [[
    56. 

  56. 5. If type is 0xFF and length is 0, then set the client terminated flag  
    57. 

  57. and abort these steps. All further data sent by the client should be  
    58. 

  58. discarded.
    59. 

  59. ]]
    60. 

  60. 

  61. and:
    62. 

  62. 

  63. [[
    64. 

  64. At any time, the server may decide to terminate the WebSocket connection  
    65. 

  65. by running through the following steps:
    66. 

  66. 

  67. Send a 0xFF byte and a 0x00 byte to the client to indicate the start of  
    68. 

  68. the closing handshake.
    69. 

  69. 

  70. Wait until the client terminated flag has been set, or until a  
    71. 

  71. server-defined timeout expires.
    72. 

  72. 

  73. Close the WebSocket connection.
    74. 

  74. ]]
    75. 

  75. 

  76. I'm confused at this point how the closing handshake is supposed to work.
    77. 

    78. 

  78. [[
    79. 

  79. Once these steps have started, the server must not send any further data  
    80. 

  80. to the server. The 0xFF 0x00 bytes indicate the end of the server's data,  
    81. 

  81. and further bytes will be discarded by the client.
    82. 

  82. ]]
    83. 

  83. 

  84. s/to the server/to the client/
    85. 

  85. 

  86. -- 
    87. 

  87. Simon Pieters
    88. 

  88. Opera Software
    89. 

  89. 

  90. </PRE>
    91. 

  91. 

  92. <!--endarticle-->
    93. 

  93. <!--htdig_noindex-->
    94. 

  94.     <HR>
    95. 

  95.     <P><UL>
    96. 

  96.         <!--threads-->
    97. 

  97. 	<LI>Previous message: <A HREF="068378.html">[whatwg] Should default styles for h1-h6 match the outlining algorithm?
    98. 

  98. </A></li>
    99. 

  99. 	<LI>Next message: <A HREF="068383.html">[whatwg] The real issue with HTML5's sectioning model (was:	&quot;Headings and sections,	role of H2-H6&quot; and &quot;Should default styles for h1-h6 match the	outlining algorithm?&quot;)
    100. 

  100. </A></li>
    101. 

  101.          <LI> <B>Messages sorted by:</B> 
    102. 

  102.               <a href="date.html#68380">[ date ]</a>
    103. 

  103.               <a href="thread.html#68380">[ thread ]</a>
    104. 

  104.               <a href="subject.html#68380">[ subject ]</a>
    105. 

  105.               <a href="author.html#68380">[ author ]</a>
    106. 

  106.          </LI>
    107. 

  107.        </UL>
    108. 

  108. 

  109. <hr>
    110. 

  110. <a href="http://lists.whatwg.org/listinfo.cgi/whatwg-whatwg.org">More information about the whatwg
    111. 

  111. mailing list</a><br>
    112. 

  112. <!--/htdig_noindex-->
    113. 

  113. </body></html>
    114.