3 ms·
What worries me, and I realized this only after trying TogetherJS, is that Websockets don't require a special permission in browsers! So any website with JS ena
by hrjet 13y ago
What worries me, and I realized this only after trying TogetherJS, is that Websockets don't require a special permission in browsers! So any website with JS enabled is now going to be able to do peer-to-peer? Could this be a can of worms, security-wise?
- TazeTSchnitzel 13y ago1. WebSockets allow real-time client-server communication. They do not allow P2P and have to follow the Same Origin Policy. 2. WebRTC allows P2P. Can't see how it's a security issue.
- esrauch 13y agoWebsockets are not subject to Same Origin Policy. In Firefox it is subject to a "must use wss:// if on a https:// https:// page", but that's all.
- TazeTSchnitzel 13y agoWhere did you get that from? They are indeed subject to it, unless CORS is in effect.
- esrauch 13y agoSorry about the delay, I didn't see your reply until now. I assume you went see mine. If you do a search for "websockets cross origin" every result says they are allowed. I currently have something running that is doing cross domain websockets and it works perfectly fine on FF and Chrome without any special effort.
- TazeTSchnitzel 13y agoAnd if you read each, it says only when using CORS.