Difference between revisions of "GstWebRTC - Advanced Settings"
m |
m |
||
| Line 1: | Line 1: | ||
| − | {{GstWebRTC/Head|previous=API Reference|next=Elements| | + | {{GstWebRTC/Head|previous=API Reference|next=Elements|metakeywords=Gstreamer WebRTC Basics,Plugin Overview,Gstreamer WebRTC Plugin Overview,Signaler,signaler-obj,WebRTC Signaler,WebRTC API,signaling}} |
==Change the Max Persistent Connections per Server== | ==Change the Max Persistent Connections per Server== | ||
Latest revision as of 10:14, 9 March 2023
 |
| GstWebRTC | ||||||||
|---|---|---|---|---|---|---|---|---|
 | ||||||||
| WebRTC Fundamentals | ||||||||
| GstWebRTC Basics | ||||||||
|
||||||||
| Evaluating GstWebRTC | ||||||||
| Getting the code | ||||||||
| Building GstWebRTC | ||||||||
| Examples | ||||||||
|
||||||||
| MCU Demo Application | ||||||||
| Contact Us |
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.
