These are chat archives for P2PSP/MediaSources-server
Hi again, I wanted to ask, what exactly is meant by "a wrapper WebService that can receive the video through an HTTP request" in this context?
Explanation: At its current state, the Splitter - which handles the team of peers - needs to be connected using an IP and Port which must be either fixed or previously agreed for both streaming video and peer connection. Which we want to accomplish here is to have a wrapper WebService that can receive the video through an HTTP request - or any other way that can easily get through NATs-, create an Splitter instance and redirect the video to it, assigning a 'friendly URL' to it that can be easily shared. When this URL is visited, it will reply with the IP and port that the peers need in order to connect to the Splitter.
<video>element, or use HTTP headers like
'Content-Range': '' , 'Accept-Ranges': ''(most widely used) or just offload this task to different protocol which bypasses HTTP and uses something like websockets(though I haven't seen this yet).
@vicente-gonzalez-ruiz sorry for bugging again but I'm having a bit difficulty understanding it. When you say -
the source of the video should transmit the video to a “Web" server which would retransmit (or redirect, this is also an option) the video to splitter.
How do you actually intend to transmit it to "Web Server"? As far I understand, there are two ways to do this -
The source could be a simple media file eg.
myMovie.mp4 lying on disk which the "Web Server" could read and transmit to splitter or the source is a separate program that gives the file address eg
/home/downloads/myMovie.mp4 to "Web Server", both of which are same thing at end.
The source is a separate program which uses some kind of networking protocol to send the video to "Web Server" which again retransmits it to splitter. If this is the case, what kind of networking protocol are we talking here?