These are chat archives for P2PSP/MediaSources-server

16th
Mar 2017
Abhinav Gauniyal
@agauniyal
Mar 16 2017 00:55
@vicente-gonzalez-ruiz this "Web" server is the Bocast server written in node, right?
Abhinav Gauniyal
@agauniyal
Mar 16 2017 01:02
I'm interested in knowing the "protocol" that Source Program will use to send/stream video to this Web Server, and the "protocol" the Web Server will use to retransmit the incoming video/buffer to the Splitter.
Assuming the "Web" server is the Bocast server written in node, we can use protocol including TCP, UDP, HTTP or anything that's built on top of these protocols.
Abhinav Gauniyal
@agauniyal
Mar 16 2017 01:12

Oh wait, are you saying that instead of

  1. Reading/Parsing the video stream and then keeping it in a buffer and then retransmitting that buffer to Splitter

  2. The Source's address eg 127.0.0.1:5555 will be sent/assigned to the newly created Splitter so the splitter does the whole work. And Web Server just maintains this list of Source <-> Splitter pair and assigns a friendly URL for each pair which on visiting returns the address of the splitter for Peers to connect to?

Abhinav Gauniyal
@agauniyal
Mar 16 2017 01:19
If it's the 2nd point instead of 1st, the problem is how would the Web Service notified of presence of Source that is streaming video? That has to be done by the Source program itself - kind of like registering itself with the Web Service that I'm streaming some video, please assign me a Splitter..
Abhinav Gauniyal
@agauniyal
Mar 16 2017 06:58
Or do you want a frontend where user could enter the source ip and source port and get a friendly url for the new/existing splitter corresponding to that source