17 ms·
In relation to #2 and #3, I think you underestimate how hard it is to get a p2p connection. It's very hard, and sometimes impossible, which is why a TURN serve
by pthatcherg 15y ago
In relation to #2 and #3, I think you underestimate how hard it is to get a p2p connection. It's very hard, and sometimes impossible, which is why a TURN server will often fallback to simply relaying data, in which case someone running the server has to pay for the bandwidth. Thus, you need to pay for a TURN server if you want to run a p2p service (or make users relay the data, like Skype does).
In relation to #4, you want the encryption to be done by the browser. Encryption is very hard to do right. You're crazy if you think you'll implement it correctly by yourself in JS.
- kragen 15y agoWRT #2 and #3, I know it's very hard; that's why it's particularly important to be able to take advantage of those few nodes that do have publicly routable addresses so that I'm not at the mercy of some bozo whose TURN server billing got screwed up. With relationship to #4, yes, I know it's hard; that's why I think it should be a JavaScript library rather than written into the spec of the browser behavior. I don't recall where I said I wanted to do anything "by myself". I rather prefer to enable open-source collaboration and decouple the security protocol from the necessarily lumbering standards process.