title: How to use HTML5's Encrypted Media Extension without video
body: <p>OK - so I understand that the Encrypted Media Extensions (EME) is all about video decrypting for the developer.
  My understanding is that EME detects when encryption is present, gets the appropriate key (with license) decrypts the content and passes it to the correct codec for rendering. </p>
  
  <p>Now - looking in a bit more detail; from this good <a href="https://developers.google.com/web/fundamentals/media/eme" rel="nofollow noreferrer">intro article on google developers</a>, and am trying to see if I can adapt the EME engine to use for streaming of non-video content.</p>
  
  <p>The challenege I'm looking into is to encrypt some static content in a way where EME can handle the keys for me, and the decryption for me.</p>
  
  <p>I'm hoping that EME is generic enough that I can hook into call-backs to serve more static content - encrypted - to the browser (since the standard only dictates interfaces of the key system, the CDM, License Server, and Packaging Service).
  The question is how would I go about doing this?</p>
  
  <p>I'm sure that we must have our own packaging service.
  But now the question extends to these details: -</p>
  
  <ul>
  <li>Do I need to make my own license server (and what are the specs for that)</li>
  <li>Can I re-use one of the Key Systems and the CDM that come with Chrome, or is there a way I should build my own?</li>
  <li>Do I have to define my own "codec" that renders the content? If yes; is there a way I can register this codec with the browser?</li>
  </ul>
  
  <p>Well - that's it in a nutshell; any advice or enlightenment is welcome.</p>