<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 06/10/2014 02:36 PM, Maciej
Stachowiak wrote:<br>
</div>
<blockquote
cite="mid:79B617BC-EC6A-48E0-AD6D-B36ED39449BE@apple.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
We have no current plans to make it an extension point for Mac or
iOS Safari or for other WebKit clients. We don’t like binary
plugins of any kind, and content providers seem satisfied with
what we can offer as built-in CDMs (for example, see <<a
moz-do-not-send="true"
href="http://techblog.netflix.com/2014/06/html5-video-in-safari-on-os-x-yosemite.html">http://techblog.netflix.com/2014/06/html5-video-in-safari-on-os-x-yosemite.html</a>>).
So we don’t see the value proposition of allowing third-party CDMs
to be plugged in.
<div><br>
</div>
<div>If you disagree with that stance and have a specific use
case, feel free to submit that feedback via <a
moz-do-not-send="true" href="http://bugreport.apple.com">bugreport.apple.com</a>
or to Apple Developer Relations. It is not really a suitable
topic to debate on webkit-dev.</div>
<div><br>
</div>
<div>Other WebKit ports may feel differently, and may want an
interface to plug in third-party CDMs. That is up to them. I
don’t have any objection to other WebKit ports using this
mechanism, I’m just reporting that it wouldn’t be especially
useful to us.</div>
</blockquote>
Ok, thanks for the info. I'll bring it up with the GTK developers
(if they support EME at all..) if we decide to move forward with
this in WebKit.<br>
</body>
</html>