Difference between revisions of "GstWebRTC - Advanced Settings"
Maumontero (talk | contribs) |
m |
||
| Line 16: | Line 16: | ||
This property is hardcoded in Chrome. In order to change this setting, you will need to recompile the browser. Alternatively, each user in Chrome could use 5 sessions so more connections could be opened with different users. | This property is hardcoded in Chrome. In order to change this setting, you will need to recompile the browser. Alternatively, each user in Chrome could use 5 sessions so more connections could be opened with different users. | ||
| − | |keywords=Gstreamer WebRTC Basics,Plugin Overview,Gstreamer WebRTC Plugin Overview,Signaler,signaler-obj,WebRTC Signaler,WebRTC API}} | + | |keywords=Gstreamer WebRTC Basics,Plugin Overview,Gstreamer WebRTC Plugin Overview,Signaler,signaler-obj,WebRTC Signaler,WebRTC API,signaling}} |
Revision as of 12:01, 14 May 2019
| ← |
⌂ Home |
→ |
Change the Max Persistent Connections per Server
The problem is that if more than 5 pages of webrtc are connected using the same browser page, the 6 will freeze but if one of the 5 is disconnected the 6 will work. That happens by the limit of http request set it by the browser.
Some possible solutions for the different browsers are:
Firefox
Write about:config in the browser and in that page search for network.http.max-persistent-connections-per-server and changed for the desired value.
Chrome
This property is hardcoded in Chrome. In order to change this setting, you will need to recompile the browser. Alternatively, each user in Chrome could use 5 sessions so more connections could be opened with different users.
| ← |
⌂ Home |
→ |
