3 ms·
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 e
by abraham 16y ago
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.
- dekz 16y agoWith the current spec, how would you listen for connections?
- abraham 16y agoThe 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.
- dekz 16y agoI don't doubt you can implement that functionality, if you were the browser. But from the specs of Websocket currently in the browser, you cannot.