[whatwg] RTSP in HTML5
chytanyak at gmail.com
Fri Aug 7 13:45:23 PDT 2009
Thanks for the quick response!
Browsers may not implement it unless it is mandated in the spec. Since
browsers already have HTTP transport, I am afraid the browsers will end up
just supporting HTTP as the only transport for the video tag. Since RTSP is
the major streaming protocol and since HTML5 is supporting multimedia
playback experience within the browser, including RTSP in the spec could
completely do away with the need to have stand-alone RTSP clients installed
or properitery plugins/solutions especially for live streaming. I think it
makes everyone's life a lot easier knowing that there is a standard player
engine present on every PC (through browser) that supports HTTP and RTSP in
multimedia tags instead of worrying about the numerous proproeitery
streaming protocols (based on HTTP) that are coming up with recently.
On Fri, Aug 7, 2009 at 1:29 PM, Ian Hickson <ian at hixie.ch> wrote:
> On Fri, 7 Aug 2009, Chytanya Karusala wrote:
> > I thought the video tag in HTML5 will point to a media resource which
> > will be downloaded by the browser and passed on to the player engine
> > inside the browser. If the src tag points to rtsp link the
> > browser/player engine wouldn't know how to handle. By including the rtsp
> > URI support in the video tag, player engine within every browser would
> > act as a rtsp client making better streaming solutions possible (viz..
> > live streaming- in addition to download/progressive download already
> > made possible by video tag)
> Ah, I see.
> The HTML5 spec doesn't say what transports are expected to be supported;
> there's no reason browsers couldn't support RTSP as well as HTTP.
> Ian Hickson U+1047E )\._.,--....,'``. fL
> http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
> Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the whatwg