4 ms·
Anyone here involved in the decision not to allow raw TCP/UDP/etc.? That would've really let us do some fun things. :) (I waned to write a self-hosting webpage
by angersock 15y ago
Anyone here involved in the decision not to allow raw TCP/UDP/etc.? That would've really let us do some fun things. :)
(I waned to write a self-hosting webpage, but WS doesn't get you there--the real-time communication stuff might, though.)
- axiak 15y agoWebsockets is designed to work over all of the existing HTTP proxy systems that currently exist. Could you imagine a system that's backwards incompatible with the world wide web? In many institutions (schools, workplaces), internet access is filtered through a proxy server.
- angersock 15y agoOh, no, I absolutely appreciate that. I'm just saddened that lower-level stuff isn't exposed. Even just TCP access and listening would be great to have--especially as raw TCP connections are pretty much the standard transport exposed for HTTP (please correct me if I'm wrong in this assumption). I'm not suggesting that it would be foolproof for consumer applications or what have you--but being able to write something like netcat in javascript for my browser would be pretty cool.
- saurik 15y ago"The protocol is not raw TCP because it needs to provide the browser’s “same-origin” security model." -- http://blog.chromium.org/2009/12/web-sockets-now-available-in-google.html http://blog.chromium.org/2009/12/web-sockets-now-available-i...