WebSocket test server migration on PPAPI tests

net/data/websocket/close-code-and-reason_wsh.py

Index: net/data/websocket/close-code-and-reason_wsh.py
diff --git a/net/data/websocket/close-code-and-reason_wsh.py b/net/data/websocket/close-code-and-reason_wsh.py
new file mode 100644
index 0000000000000000000000000000000000000000..6ebf821e96b3e84767db6dd8fd943246c887dd76
--- /dev/null
+++ b/net/data/websocket/close-code-and-reason_wsh.py
@@ -0,0 +1,25 @@
+# Copyright (c) 2012 The Chromium Authors. All rights reserved.

[Paweł Hajdan Jr., 2012/10/16 17:01:27]

Why is code in net/data? I think net/tools or net/test (depending on what it is)
would be better place.

[Takashi Toyoshima, 2012/10/17 01:28:32]

As you said, net/test/data is better place to have this kind of test data, and
other component follow that rule.
But, actually, we already have many resources for testing in net/data. So, I
just follow it in this series of CLs.

If we must have in net/test/data, we should make another refactoring change with
separated bug entry.

+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+import struct
+
+from mod_pywebsocket import stream
+
+
+def web_socket_do_extra_handshake(request):
+  pass
+
+
+def web_socket_transfer_data(request):
+  line = request.ws_stream.receive_message()
+  if line is None:
+    return
+  if line == '-':
+    data = ''
+  elif line == '--':
+    data = 'X'
+  else:
+    code, reason = line.split(' ', 1)
+    data = struct.pack('!H', int(code)) + reason.encode('utf-8')
+  request.connection.write(stream.create_close_frame(data))