We are watching HTML5 videos for delivering interactive videos, such as managing videos using hyperlinks (for example, allowing the user to navigate to parts of the video that have not yet been uploaded), and also JavaScript responds to events from the video (for example, something happens when video reaches 00:25).
For test videos, this seems possible in libraries like Video.js, and provides a decent working experience in modern browsers.
I have been reading text from 2009, which seems to indicate that in the near future (perhaps today) that modern browsers will catch up and exceed the capabilities of streaming protocols and servers:
RTSP is designed for video communications, similar to applications that support voice over IP. This is not the best protocol for streaming on demand, where HTTP with byte range requests achieves the same result. Additional functionality supported by RTSP is also becoming more accessible using innovative HTTP approaches. Only an operational communication case is one that may require the implementation of RTP / RTSP over UDP to work with the required low latency.
RTSP-like streaming approaches that require a dedicated server and client software are increasingly failing in a world dominated by HTTP. For example, YouTube is fully available through progressive HTTP downloads and does not use RTMP. In this situation, providers use progressive HTTP downloads and have developed their own feature extensions to improve HTTP-based streaming.
In what future are streaming protocols such as RTSP / RTMP and streaming video servers such as Adobe Streaming Server available when they are visible given the increasing capabilities that browsers add to support HTML5 video?
source share