[webkit-dev] Trying to turn WebRTC's code on - MEDIA_STREAM flags
agouaillard at gmail.com
Sun Aug 24 08:37:39 PDT 2014
For clarification of the goals and the scope, we intend to provide patches
in webkit for webRTC. We would love to see webRTC support in iOS and we
understand that having it in apple provided webkit (UIWebView) to comply to
apple store rule 2.17. We understand we do not have complete control over
the entire process, especially the eventual packaging and deployment, and
the timelines, and that apple does not comment about this, but we thought
implementing it in webkit was a necessary prerequisite in any case. For the
rest we will have faith :-)
During a phone conversation with eric C, we've ben told that we should
start by making it happen in the macOS X port as we would snot be able to
build for iOS and because the differences were not so big between the iOS
and the macOS ports.
JO has been working on the Media Capture and Stream and webRTC APIs for
almost a year, and developed an IE and Safari plugin that implements all of
the APIs. He reads/speaks/write web IDL fluently now, and now all the
subtleties of the constraints, streams, tracks, ect. I sit at the standard
committees and help with everything that is not clear from the specs.
Unfortunately, that does not help understand webkit intricacies and that's
where we are today.
We reached out to Eric C, Thiago from nokia (NIX port), kirun from samsung,
and started from there. I also speak regularly with adam Be. from ericson
at the w3c meetings. I will jump in the project and add an additional
senior staff, so we should be 2~3 FTE starting tuesday. Looking at philippe
N works in WK2, it looks like you would be a reviewer of any patch we would
submit, correct? (bug <https://bugs.webkit.org/show_bug.cgi?id=123158>)
With our target (iOS/MacOS X) should we target WK1 or WK2? We plan to
finalize the webcore part first, but we need to target an app, and a port
for testing. NIX does not seem to be an option anymore.
There also seem to have been a discussion about the design (platform vs
client) triggered by adam Be.. Anybody knows if there was a conclusion? (bug
<https://bugs.webkit.org/show_bug.cgi?id=67946>) We would prefer putting a
maximum of common code in webcore, as proposed by adam.
We are also contributing some tests to w3c (based on testharness.js,
testing the bindings and IDL only) that we plan to use for testing.
Dominique has recently committed the tests for steams and tracks using the
latest spec (here
Is there anything we should prepare in the layout tests for this as well?
It looks like the media stream tests have been excluded from the tests for
the time being.
We are trying to have a working implementation by oct 15th, so we could
send it for test around and get feedback in time for discussion during the
W3C technical plenary and advisory committee meeting on oct. 27th, in San
looking forward to any feedback.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev