Does WebRTC use TCP or UDP ?

[Khoa Pham]

Hi, this sounds like a basic question, but I need a confirmation

1. Does WebRTC uses TCP or UDP as its transport? How do I know ?

Is this transport the same for both Media and DataChannel ?

2. If I want to make webrtc connection to many other peers, should I create many RTCPeerConnection?

I heard that on Chrome, the limit on max parallel connections are 8. I think this does not apply to UDP

Many thanks

[Vikas]

On Thursday, September 19, 2013 7:35:45 AM UTC-7, Khoa Pham wrote:

Hi, this sounds like a basic question, but I need a confirmation

1. Does WebRTC uses TCP or UDP as its transport? How do I know ?

Is this transport the same for both Media and DataChannel ?

This really depends on the network configuration, for eg if UDP is blocked TCP might be used. I think you can get that information from chrome://webrtc-internals by looking at the candidates and the googActiveConnection. I would guess the transport would be same for media & data.

2. If I want to make webrtc connection to many other peers, should I create many RTCPeerConnection?

I heard that on Chrome, the limit on max parallel connections are 8. I think this does not apply to UDP

Yes, you would need to create multiple Peerconnections if you want to connect to multiple peers. AFAIK, there is no such limit.

Many thanks

[MadWizard]

четверг, 19 сентября 2013 г., 17:35:45 UTC+3 пользователь Khoa Pham написал:

2. If I want to make webrtc connection to many other peers, should I create many RTCPeerConnection?

I heard that on Chrome, the limit on max parallel connections are 8. I think this does not apply to UDP

Many thanks

Last time i checked, i could create about 50 active RTCPeerConnection's in firefox and about 100 in chrome

[Vikas]

Hi,

What version of chrome you tested with? As per issue 1343, there was a limit to KMaxViECaptureDevices which was bumped to 256. I have not tested creating that many peer connections but let us know if you getting some sort of error.

/Vikas

[Alexandre GOUAILLARD]

Sending reasonable audio/video streams (QVGA), on a normal computer, you're likely to hit a CPU overload problem before hitting the hardcoded 256 PCs limit. Depending on your hardware, a guesstimate would be 10~20. If you do audio only, you're likely to scale much better.

--
 
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.