Why do we need any middleman if i can directly communicate to second computer. That's how Peer to peer communication works. You just need initial signaling to be done with the help of server.
Create an offer from computer initiating communication, pass it to server which in turn check same with peer computer. Once peer acknowledge incoming request, it will share its SDP details.
Once acknowledgement received with peer connection information, computer will be able to directly communicate with peer.
Now in this post, I wish to talk about how WebRTC will be leveraged to implement multiparty video conferencing.
Mesh:
In this architecture every participant have a connection to each other. So for n participant will have n-1 connection. So total n*(n-1)/2 connections. This is easy to implement as it does not need much changes from existing P2P connection. All the stream handling is done at edge computer. It has drawback of high data consumption and scalability issues.
Routing:
In this architecture all participant will be sending their stream to central server which in turn will be sending to other participants. It is scalable and but could be costly.
Mixing:
In this architecture all participant will be sending their stream to central server which in turn consolidate them in single stream and will be sending single stream to all participants.
It is scalable but costly as server has to do a lot of stream processing. .
Create an offer from computer initiating communication, pass it to server which in turn check same with peer computer. Once peer acknowledge incoming request, it will share its SDP details.
Once acknowledgement received with peer connection information, computer will be able to directly communicate with peer.
Now in this post, I wish to talk about how WebRTC will be leveraged to implement multiparty video conferencing.
Mesh:
In this architecture every participant have a connection to each other. So for n participant will have n-1 connection. So total n*(n-1)/2 connections. This is easy to implement as it does not need much changes from existing P2P connection. All the stream handling is done at edge computer. It has drawback of high data consumption and scalability issues.
Routing:
In this architecture all participant will be sending their stream to central server which in turn will be sending to other participants. It is scalable and but could be costly.
Mixing:
In this architecture all participant will be sending their stream to central server which in turn consolidate them in single stream and will be sending single stream to all participants.
It is scalable but costly as server has to do a lot of stream processing. .
Comments
Post a Comment