26386 2014-07-19 13:37:23 +0000 Since WebSocket is still in development, I propose in addition to "ws" and "wss", you also include " [...] 2014-07-19 16:44:13 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#top P3 normal Unsorted 1 contributor ian ian mike contributor oldest_to_newest 109103 0 contributor 2014-07-19 13:37:23 +0000 Specification: http://dev.w3.org/html5/websockets/ Multipage: http://www.whatwg.org/C#top Complete: http://www.whatwg.org/c#top Referrer: Comment: Since WebSocket is still in development, I propose in addition to "ws" and "wss", you also include "tcp" and "udp" protocol headers that will allow for connecting without a WebSocket handshake (raw connections). That would greatly increase compatibility with existing services. This is currently a major barrier to it's usage. A cryptography API would go along well with that, since even if someone does write libraries in JavaScript, they would have major performance issues. That would provide legacy support for mail servers that require starttls. Posted from: 94.190.193.97 User agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.153 Safari/537.36 109110 1 ian 2014-07-19 16:44:13 +0000 Connecting without a handshake is a non-starter: it would be a security disaster.