Yes. It took some effort on our server side for us to support Firefox with DTLS (still incomplete) as compared to Chrome with vanilla signaling. I believe we have long way to build interop in browsers: RTP, JS API and maybe Signaling (with webserver). ScreenSharing policy is yet to be resolved. I see this discussion is stuck at JS API vs JS SDP API, while equally important standards like screensharing policy are in queue. regards, Rishi On Mon, Jul 22, 2013 at 11:49 PM, tim panton <thp@westhawk.co.uk> wrote: > > On 22 Jul 2013, at 18:45, Roman Shpount <roman@telurix.com> wrote: > > On Mon, Jul 22, 2013 at 1:00 PM, Philipp Hancke <fippo@goodadvice.pages.de > > wrote: > >> I said this before, but since you insist on repeating your argument i'll >> repeat mine: I have running code doing exactly that. >> >> It's hard work and there are some points where this is PITA, I have >> discovered numerous bugs in chrome (and the jingle spec) along the way, but >> it's certainly not unfeasible. >> >> > Out of curiosity, does the same code work with Firefox? > > > As far as Phono is concerned - yes - but we had to do some work to make > that happen, more > work in fact than adding DTLS on the server side, which is (frankly) > absurd. > > T. > > > > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb > >
Received on Thursday, 25 July 2013 10:44:16 UTC