81–87 of 87 posts
Earlier quoted context omitted.
Well, maybe you should contact Microsoft and ask them to provide a port or provide similar functionality. Your users have, after all, paid Microsoft for the privilege of using IE.
Last time I checked IE was free.
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?
1. 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.
Earlier quoted context omitted.
1. 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.
Websockets are not subject to Same Origin Policy. In Firefox it is subject to a "must use wss:// if on a https:// page", but that's all.
Earlier quoted context omitted.
It's comments such as this that bubble up to the top of the comment chain that often makes me wonder if only a minority of HN users have deployed to enterprise environments with rigid infrastructure policies. In my more cynical moods I wonder what percentage of users have non-novelty code in production at all.
Fair enough. If you need to support outdated browsers because of someone else's technology choices, that's a differentiating feature for you and your business, and I respect that (and I hope you're charging a decent amount as compensation for the fact you're supporting their older technology). But if you're interested in the advance of technology, especially when it's pushing the boundaries, a little bit (or a lot) o…
Earlier quoted context omitted.
Websockets are not subject to Same Origin Policy. In Firefox it is subject to a "must use wss:// if on a https:// page", but that's all.
Where did you get that from? They are indeed subject to it, unless CORS is in effect.
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.
Earlier quoted context omitted.
Where did you get that from? They are indeed subject to it, unless CORS is in effect.
Sorry 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.