3 ms·

The open-source variant does not support P2P sessions if I understand it correctly, which is weird since that is half the point of WebRTC.

memco 7y ago
Yeah, I'm a little confused about this as well. It's also not clear if the demos can be used as is. I would use this for an ad-hoc meeting with friends if there's no restrictions. Given that they don't mention it maybe that's fine? I'd be willing to go through the steps to set this up on my own server, but why do I need to if this site already provides everything I need?
- j1elo 7y ago
  The demos run over a shared instance of a server with fixed resources, so I wouldn't count on it being the most stable experience, especially if it becomes popular enough to saturate the machine's resources. The intention of these demos is just to provide a showcase of the types of applications that a developer might be able to build, using OpenVidu.
giancarlostoro 7y ago
It says "without a media node", when you hover over the info or "i" icon next to P2P.
- SahAssar 7y ago
  Yeah, which implies that the free version routes all media over the server (a media node), hence it not being P2P. Not sure if you are agreeing with what I said or not?
  - giancarlostoro 7y ago
    I am just as confused honestly.
AceJohnny2 7y ago
even for P2P, WebRTC most often still requires outside servers for STUN/TURN, because everyone's behind a NAT of firewall.
- SahAssar 7y ago
  IIRC most large scale deployments have it at around 75-95% of traffic that only requires STUN (which is only used for the handshake & holepunching, not for the actual traffic). TURN is used for the remaining 25%-5%. STUN is cheap, easy and does not require a lot of traffic. TURN on the other hand requires a lot of bandwidth, which can be expensive.
j1elo 7y ago
Thing is, while WebRTC per-se is a nice standard for p2p, the actual limitations of technology (i.e. bandwidth) in the real world mean that sessions with 4 or more participants become unusable very quickly as the number of people increments. So, 99% of "serious" use cases end up requiring a centralized relay, anyway. Tsahi Levent-Levi covered this topic: https://bloggeek.me/how-many-users-webrtc-call/ https://bloggeek.me/how-many-users-webrtc-call/

memco 7y ago

Yeah, I'm a little confused about this as well. It's also not clear if the demos can be used as is. I would use this for an ad-hoc meeting with friends if there's no restrictions. Given that they don't mention it maybe that's fine? I'd be willing to go through the steps to set this up on my own server, but why do I need to if this site already provides everything I need?

j1elo 7y ago
The demos run over a shared instance of a server with fixed resources, so I wouldn't count on it being the most stable experience, especially if it becomes popular enough to saturate the machine's resources. The intention of these demos is just to provide a showcase of the types of applications that a developer might be able to build, using OpenVidu.

giancarlostoro 7y ago

It says "without a media node", when you hover over the info or "i" icon next to P2P.

SahAssar 7y ago
Yeah, which implies that the free version routes all media over the server (a media node), hence it not being P2P. Not sure if you are agreeing with what I said or not?
- giancarlostoro 7y ago
  I am just as confused honestly.

AceJohnny2 7y ago

even for P2P, WebRTC most often still requires outside servers for STUN/TURN, because everyone's behind a NAT of firewall.

SahAssar 7y ago
IIRC most large scale deployments have it at around 75-95% of traffic that only requires STUN (which is only used for the handshake & holepunching, not for the actual traffic). TURN is used for the remaining 25%-5%. STUN is cheap, easy and does not require a lot of traffic. TURN on the other hand requires a lot of bandwidth, which can be expensive.

j1elo 7y ago

Thing is, while WebRTC per-se is a nice standard for p2p, the actual limitations of technology (i.e. bandwidth) in the real world mean that sessions with 4 or more participants become unusable very quickly as the number of people increments. So, 99% of "serious" use cases end up requiring a centralized relay, anyway. Tsahi Levent-Levi covered this topic: https://bloggeek.me/how-many-users-webrtc-call/ https://bloggeek.me/how-many-users-webrtc-call/