I have done streaming of video using the older version of mongoose in a few ways. I had one server for live and recorded video. The HLS streaming was all done in memory and the files were virtual, As long as you keep updateing the links in the index file and keep serving out the segments it works great. It was shelved mostly becasue for live video it introduces additional delay.
The main streaming was just a multipart mime connection serving out an infinitly long reply with boundry headers between video frames. In my case I had a browser plugin that consumes the frames, decodes and displays them. For the most part, the plugin didn't know or care if the http traffic was from a file or live. I also was able to flip a bit on each end and do all the video over https. It added about 25% overhead. I have not tried rewriting to use the new mongoose server so there would be some changes there. RTSP is very similar to HTTP in a lot of ways. On Wed, Aug 13, 2014 at 4:46 PM, Kelvin Ishigo <[email protected]> wrote: > We have used mongoose to stream HLS. For adaptive streaming like HLS and > DASH, the stream is already broken into smaller "chunks" by the software > that originates the stream. > > > On Wed, Aug 13, 2014 at 1:27 PM, Sergey Lyubka <[email protected]> wrote: > >> On Wed, Aug 13, 2014 at 9:25 PM, Anu P <[email protected]> wrote: >> >>> Thanks Sergey. >>> >>> This means that the media file will be treated as a normal file and >>> doesn't need any media processing at web server. When HTTP get request is >>> received, the file will be written as smaller chunks to the sending socket. >>> Client has to decode the chunks received and play in sequence. How Mongoose >>> decides the segment size(chunk of media file) to be replied for ? >>> >> >> Mongoose doesn't chunk the file. >> When static file is requested, Mongoose sends HTTP headers with mime-type >> and content length, then it sends the body as a single blob with the file >> contents. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "mongoose-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/mongoose-users. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "mongoose-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/mongoose-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "mongoose-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mongoose-users. For more options, visit https://groups.google.com/d/optout.
