mohit810 / webrtc_api

1 stars 0 forks source link

Signaling plans #3

Open Sean-Der opened 3 years ago

Sean-Der commented 3 years ago

Do you want to use socket.io or plain websockets?

Long term how do you see sessions? Do you want 'rooms' and each room has 1 broadcaster, and many viewers?

Do you want chat between users/metadata etc..?

mohit810 commented 3 years ago

I have experience in using socket.io at front end in web, android dev I prefer socket.io but I am wasn't able to setup a signalling server in socket.io. So had to setup signalling router via api calling. In long term I want to implement usage of socket.io for chatting and signalling (if possible), If I move forward with current signalling set up then I will set up socket.io for chatting only.

About the part 1 broadcaster and many viewer - I am thinking of serving video and audio of broadcaster in two ways(please help me choose) :- 1) converting the stream via ffmeg to hls in different qualities and push the stream to cdns 2) directly show the broadcast.