Notify WebSocket connection failure, chromium side

content/common/websocket_messages.h

Index: content/common/websocket_messages.h
diff --git a/content/common/websocket_messages.h b/content/common/websocket_messages.h
index 5a9304f8a700888fcfc2b5c7b72fdf566ac5341e..0450b9c475c16b8e2df8ec463ab45abb584ed2e2 100644
--- a/content/common/websocket_messages.h
+++ b/content/common/websocket_messages.h
@@ -100,6 +100,8 @@ IPC_MESSAGE_ROUTED1(WebSocketMsg_FlowControl,
 // UTF-8 encoded string which may be useful for debugging but is not necessarily
 // human-readable, as supplied by the server in the Close or DropChannel
 // message.
-IPC_MESSAGE_ROUTED2(WebSocketMsg_DropChannel,
+// |fail| is true when the user agent is required to fail the connection.

[Adam Rice, 2013/10/23 03:18:06]

I think this comment needs more explanation. How about:

If |fail| is true on a message from the browser, then the WebSocket connection
was not closed cleanly. If |fail| is true on a message from the renderer, then
the connection should be closed immediately without a closing handshake and the
renderer cannot accept any new messages about this connection.

[yhirano, 2013/10/23 05:42:23]

Thanks, done.

+IPC_MESSAGE_ROUTED3(WebSocketMsg_DropChannel,
+                    bool /* fail */,
                     unsigned short /* code */,
                     std::string /* reason */)