Re:P2P API Discovered in Latest Builds of Chromium
by abraham on Saturday March 12, 2011 @03:14AM
(#2316354)
The websockets speck is still in draft. Nothing is impossible and there is no reason a browser could not implement their own extension of websockets to enable p2p. Have some imagination.
Re:P2P API Discovered in Latest Builds of Chromium
by lambda on Saturday March 12, 2011 @03:23AM
(#2316368)
I thought you were talking about websockets as it exists today, not some hypothetical future extension. See my reply in the other thread about why that might not be a good idea.
Re:P2P API Discovered in Latest Builds of Chromium
by abraham on Saturday March 12, 2011 @10:04PM
(#2318168)
Of course I'm talking hypothetical. The original article is about an experimental p2p feature in an open source browser that is several months at a minimum from even being in a beta release of Chrome.
The key is that websockets are limited in what they can do; the API and protocol are fundamentally designed in such a way as to make peer-to-peer communication impossible. It opens up possibilities that XMLHTTPRequest does not, but it does not allow you to do everything you could do with raw socket access.
There main reason it is impossible to do peer to peer with websockets is that you can't listen for incoming websocket connections using the websocket API; you can only initiate outbound connections, which connect to a server not written in a browser, as there are no APIs in the browser for listening for inbound connections.