Oh, that's cool! Didn't know that! Maybe we should create an example app showing how that works. I'd even volunteer to do that. :-)
On Thu, Jan 6, 2011 at 4:49 PM, Henry Minsky <[email protected]> wrote: > There's that whole mechanism in the HTTP request and response header is > supposed to indicate what mime types your client accepts, and even has > priorities you can specify in order of preference > > Accept: audio/*; q=0.2, audio/basic > > > But I don't know how many people there are who can and will configure their > server to respond properly to these requests. I'm guessing most servers > won't be set up correctly for this. > > > > On Thu, Jan 6, 2011 at 5:34 AM, Raju Bitter < > [email protected]> wrote: > >> One question is, how would you dynamically set the source file for a video >> at runtime? Will there be meta information available to detect which the >> preferred encoding format for the current browser will be? >> >> >> On Thu, Jan 6, 2011 at 3:24 AM, Henry Minsky <[email protected]>wrote: >> >>> I opted into the beta You Tube HTML5 player option, and it gives a little >>> summary of the browser support >>> for video formats out there now: >>> >>> Supported Browsers >>> >>> We support browsers that support both the video tag in HTML5 and either >>> the h.264 video codec or the WebM <http://webmproject.org/> format (with >>> VP8 codec). These include: >>> >>> - Firefox 4 (WebM, Beta available >>> here<http://www.mozilla.com/en-US/firefox/beta/> >>> ) >>> - Google Chrome (WebM and h.264) >>> - Opera 10.6+ (WebM, Available >>> here<http://www.opera.com/browser/download/> >>> ) >>> - Apple Safari (h.264, version 4+) >>> - Microsoft Internet Explorer 9 (h.264, Beta available >>> here<http://ie.microsoft.com/testdrive/> >>> ) >>> - Microsoft Internet Explorer 6, 7, or 8 with Google Chrome Frame >>> installed (Get Google Chrome >>> Frame<http://code.google.com/chrome/chromeframe/> >>> ) >>> >>> >>> >> > > > -- > Henry Minsky > Software Architect > [email protected] > > >
