Re:P2P API Discovered in Latest Builds of Chromium
by patrickaljord on Saturday March 12, 2011 @12:42AM
(#2316132)
You can't run a Websocket server on your browser. Only a client. So you can't get p2p by definition because in a p2p network every node is a server.
[ Parent
| on HN ]
Re:P2P API Discovered in Latest Builds of Chromium
by abraham on Saturday March 12, 2011 @01:01AM
(#2316153)
Why wouldn't you be able to run the browser as a websocket server? A browser can run everything on a computer a p2p node can.
Re:P2P API Discovered in Latest Builds of Chromium
by dekz on Saturday March 12, 2011 @02:07AM
(#2316249)
In the WebSocket spec, it only exists to open a connection to a url on a port, there is nothing about listening to a port for connections. You could open a connection to a server which can relay other websockets data, but you can't open a connection to another client. There is nothing in the spec to create a server basically.
Re:P2P API Discovered in Latest Builds of Chromium
by abraham on Saturday March 12, 2011 @02:14AM
(#2316262)
That doesn't make any sense. The browser server just responds to websocket requests the same way a server would. The other browsers acting as clients wouldn't even need to know it was a browser just that it was acting as a websocket server.
Re:P2P API Discovered in Latest Builds of Chromium
by dekz on Saturday March 12, 2011 @02:19AM
(#2316273)
With the current spec, how would you listen for connections?
Re:P2P API Discovered in Latest Builds of Chromium
by abraham on Saturday March 12, 2011 @02:40AM
(#2316305)
The same way that websocket servers currently listen for connections. There are websocket servers in production and they have a standard way to listen for connections. All you would have to do is implement that same functionality.