You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 3, 2021. It is now read-only.
The current WebRTC system that we have developed is basically a P2P mesh which is not scalable to any extent. Every connection has to be connected to every other connection in it which means nC2 connections for n users. This would mean a huge load on every user's bandwidth and outright unusable for many.
We need a monitoring system with a many-to-one architecture i.e. video stream of the students (many) would be viewed by the invigilator (one). If you have any suggestions drop them in the replies below
The text was updated successfully, but these errors were encountered:
The current WebRTC system that we have developed is basically a P2P mesh which is not scalable to any extent. Every connection has to be connected to every other connection in it which means nC2 connections for n users. This would mean a huge load on every user's bandwidth and outright unusable for many.
We need a monitoring system with a many-to-one architecture i.e. video stream of the students (many) would be viewed by the invigilator (one). If you have any suggestions drop them in the replies below
The text was updated successfully, but these errors were encountered: