Comments on: Temasys’ Free WebRTC Plugin for Internet Explorer and Safari

By: Tsahi Levent-Levi

Tsahi Levent-Levi — Wed, 04 Mar 2015 21:27:15 +0000

It would be best to ask Temasys directly in their mailing list for this: https://groups.google.com/forum/#!forum/temasys-discuss-webrtcplugin

By: Sasikumar

Sasikumar — Wed, 04 Mar 2015 20:05:07 +0000

Hi-

I am using Temasys’ Free WebRTC Plugin in my project with web audio APIs to get the audio stream. It works on all the browsers except Safari which is complaining about “createMediaStreamSource” of “AudioContext” is undefined.

Please let me know when this API will be available for Safari.

Thanks,

By: Tsahi Levent-Levi

Tsahi Levent-Levi — Thu, 31 Jul 2014 19:03:34 +0000

In reply to Brian Shock.

Brian,

Not going into too much detail about the legal aspects behind open source license types, the rule of thumb goes like this:

* BSD, MIT, APL (Apache) – good
* LGPL – it depends
* GPL, APL – bad

I might just write a post explaining it and the reasons at some point in the future.

By: Brian Shock

Brian Shock — Thu, 31 Jul 2014 19:00:49 +0000

You mentioned that webrtc4all’s GPLv3 license would make it hard for most enterprises to adopt. My knowledge of legal matters is very limited, but I’ve been trying to research the topic on Gnu.org’s web site. This is slow going for me, so could you or someone else please expand on which points of the GPLv3 present a problem for enterprises?

Thank you.

By: Lawrence Byrd

Lawrence Byrd — Mon, 12 May 2014 16:51:31 +0000

This is good news and an excellent contribution from Temasys. In my experience it is absolutely an obstacle in talking to enterprises about deploying WebRTC that IE support remains an issue (and Safari sometimes but depends on the organization). Microsoft and Apple obviously know this, hence their stalling tactics until they feel they are in an advantageous position to introduce whatever version of WebRTC we have gotten to by then. Meanwhile we can get some plugins (usually for IE but less so for Safari) from some of the other toolkit vendors, but they come wrapped up with that toolkit’s APIs, backend and licensing structure. So hats off to Temasys for being willing to develop and make available a “pure” and free set of core Windows/Mac IE/Safari ready-to-go binary WebRTC plugins. Now I know plugins are still a pain and worse than built-in functionality, but done well they are much better than WebRTC not working! (I don’t happen to believe that “no plugins” is the essential differentiator for WebRTC, just one valuable feature.)

Now my personal ideal would be if a number of toolkit vendors were willing to work together with Temasys so that a single plugin (that is, a single set of plugins across platforms) could be declared to be “standard” across multiple vendors. I don’t know if other vendors are now willing to do this, given their other plans,or if Temasys is willing to be “joined”. But my view is that if the industry was showing a common agreed approach to bridging the IE and Safari “gap” then this would make adopting enterprises even more comfortable, while reducing the number of different plugin downloads for different applications (“get it once” and be done).

By: Tsahi Levent-Levi

Tsahi Levent-Levi — Mon, 12 May 2014 14:06:57 +0000

In reply to Philipp Hancke. which is the only reason why I decided to spend the time to write about it :-)

By: Philipp Hancke

Philipp Hancke — Mon, 12 May 2014 14:06:10 +0000

one of the most interesting aspects is that the plugin doesn’t attempt to come up with it’s own APIs but just wraps the usual RTCPeerConnection and getUserMedia.

By: Alex Gouaillard

Alex Gouaillard — Mon, 12 May 2014 13:40:29 +0000

Thanks tsahi for the post. We hope this will indeed enable developers and help the community gain in recognition. We also want to publicly thanks bistri (bistri.com), for dedicating some time to help us polish the plugin. Thank you for helping us making this happen.