1. katiepea's Avatar
    if any of you read my posts, i'm a STRONG advocate for apps and dont' consider the browser a replacement for them. at any rate. this bit of news should be great for bb users.

    Netflix coming to HTML5 just as soon as the DRM ducks are in a row

    Netflix users on Windows and OS X currently depend on Microsoft's Silverlight plugin to watch videos. With Silverlight no longer under active development, the company is looking at alternative delivery systems for its app-free, browser-based video delivery.

    The answer it's picked is, unsurprisingly, HTML5, but as the company details in a blog post, it's not up to the challenge just yet. The sticking point, again unsurprisingly, is DRM. Netflix's Silverlight player protects the content that it plays, and the company needs to maintain a similar level of protection in its HTML5 successor.

    That isn't possible today, but with a trio of features currently being worked on under the remit of W3C, the World Wide Web Consortium, it soon will be.

    Two of the features are relatively uncontentious. The <video> element that underpins HTML5-based video playback presently uses a specific URL or URLs as its data source. Netflix, however, performs dynamic management of the source, so that, for example, it can switch to lower bitrate streams if it detects a deterioration in network conditions. The Media Source Extensions (MSE) extends the <video> element to give JavaScript this kind of control.

    The Web Cryptography (WebCrypto) API provides a JavaScript API for various standard cryptographic features such as hashing and encryption. This can be used for many things, such as client-side encrypted data storage, client-side generation of signed documents and e-mail message, and client-side secure instant messaging.

    The third feature is, however, for many people unwelcome. Encrypted Media Extensions (EME) provide an API that allows using encrypted media streams with HTML5's <video> and <audio> tags. EME defines how HTML5 browsers will detect that encrypted streams are being used, and then look up an appropriate Content Decryption Module (CDM) that will verify that the license is being properly respected, and then decrypt the data.

    The announcement in February that W3C had deemed EME to be in scope for HTML5's development, and hence something that can be developed under W3C's banner, was not universally welcomed by the Web community. Content owners, and some of those providing services to content owners (both directly, such as Netflix, and indirectly, such as Microsoft and Google, with Internet Explorer and Chrome, respectively) regard EME as either desirable, or at least necessary, if premium video content is to move to HTML5.

    For them, the choice is between "Silverlight/Flash/custom apps with DRM" and "HTML5 with DRM." "HTML5 without DRM" simply isn't in the running.

    Countering that group are those who say variously that DRM is ineffective, DRM undermines users' rights, and that CDMs allow non-standard, proprietary code to be injected into the browser. In that light, it serves much the same role as plugins anyway, and as such, EME contradicts the goals of the open Web. Most or all CDMs are likely to be proprietary, unmodifiable code, to reduce the chance that they are tampered with.

    Currently, the Chrome browser and Chrome OS have preliminary support for MSE and EME. Netflix is using both of these on Chrome OS to provide Netflix video to Chromebook users. It's using a plugin for WebCrypto; once that's included in Chrome, the plugin will be removed. From there, Netflix will begin testing its HTML5 player in Chrome on both Windows and OS X.
    allengeorge likes this.
    04-15-13 09:21 PM
  2. Bla1ze's Avatar
    It is interesting however it's all still some BS mixed with reality. If you install the Netflix for Android .bar file and sniff the traffic off your device, you can see it pinging home. Netflix right now has a website that will work in browsers. The authentication used for that site is held within the app. That's why even if you have the URL (which can be pulled out by sniffing the packets) you can't access it - say from your Z10 browser. A lot of people failed to notice the Android .bar that appeared was essentially and old beta version that offers boot options, playback options and even offers up Netflix's test URL for video playback access pretty much anywhere without the need for Silverlight.
    stabstabdie likes this.
    04-15-13 09:29 PM
  3. katiepea's Avatar
    It is interesting however it's all still some BS mixed with reality. If you install the Netflix for Android .bar file and sniff the traffic off your device, you can see it pinging home. Netflix right now has a website that will work in browsers. The authentication used for that site, is held within the app. That's why even if you have the URL (which can be pulled out by sniffing the packets) you can't access it - say from your Z10 browser.
    well that's where the DRM comes in, i don't think netflix would deny that it could work right now, but the content providers would go ballistic until a deal is struck allowing them to do so. netflix's hands are tied until such a deal exists. they have to protect the content how the providers want or they couldn't operate.
    04-15-13 09:31 PM
  4. Bla1ze's Avatar
    well that's where the DRM comes in, i don't think netflix would deny that it could work right now, but the content providers would go ballistic until a deal is struck allowing them to do so. netflix's hands are tied until such a deal exists. they have to protect the content how the providers want or they couldn't operate.
    Ya, totally. I don't hold Netflix to 'blame' for any of it really. It's all on big media and the content providers.
    04-15-13 09:36 PM
  5. stabstabdie's Avatar
    It is interesting however it's all still some BS mixed with reality. If you install the Netflix for Android .bar file and sniff the traffic off your device, you can see it pinging home. Netflix right now has a website that will work in browsers. The authentication used for that site is held within the app. That's why even if you have the URL (which can be pulled out by sniffing the packets) you can't access it - say from your Z10 browser. A lot of people failed to notice the Android .bar that appeared was essentially and old beta version that offers boot options, playback options and even offers up Netflix's test URL for video playback access pretty much anywhere without the need for Silverlight.
    You so smart.
    Thanks again for the bar!
    04-17-13 04:58 PM

Similar Threads

  1. ask.com coming up for dictionary.com search in browser
    By bbearhug in forum BlackBerry Storm Series
    Replies: 2
    Last Post: 06-08-09, 08:23 PM
  2. Question for the gurus..Autotext in Browser?
    By cervoni in forum BlackBerry Storm Series
    Replies: 0
    Last Post: 03-15-09, 08:18 PM
  3. ok button greys out when i select notes for address book in pim
    By AMighty1 in forum BlackBerry Secure UEM & Productivity Suites
    Replies: 0
    Last Post: 08-22-08, 12:50 PM
  4. BETA Test for those in NYC, new browser
    By SLVR6 in forum General BlackBerry News, Discussion & Rumors
    Replies: 5
    Last Post: 07-09-08, 08:51 PM
  5. Flash Player for viewing videos in browser
    By Lightblueness in forum BlackBerry 88xx Series
    Replies: 1
    Last Post: 11-08-07, 07:26 AM
LINK TO POST COPIED TO CLIPBOARD