Linked by David Adams on Wed 9th Nov 2011 06:34 UTC
Permalink for comment 496738
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
More News »
Sponsored Links



Member since:
2010-06-02
I know having raw TCP support in HTML isn't a good idea.
I do like the way Flash gets around it: it makes a request to the target on port 587 before initiating the TCP socket, and expects an XML security certificate permitting the connection. That means you have to authorise it on the server-side, but aside from that it doesn't actually interfere with the stream. So if you wanted to make e.g. a web-based IRC client, you could use a standard IRCd and no websocket proxy, just run an authenticating script on that port to demonstrate you consent to the connections.
Anyways, raw TCP is a legitimate feature that Flash has over HTML, and Flash is still worth considering in certain situations.