The plan is to have the P2P VC WebKit code to do as little as possible and leave the implementation to the browser port, just like the MediaStream patches. And the code touches very little other code; Event, EventTarget, Navigator etc but obviously heavily depends on the MediaStream functionality.
Is this a problem? Happy to modularize the functionality if someone can give me some pointers, show our work in progress etc. To get the standard (on whatwg) finalized an implementation is needed so that some real world usage can be had, and previously we have received some favorable comments re go-ahead on implementation. Personally I think this is a great feature and are committed to implement it properly. /Tommy On Sat, May 14, 2011 at 01:50, Adam Barth <aba...@webkit.org> wrote: > One approach we talked about at the contributor's meeting to dealing > with the ever-growing feature list of WebCore is modularity. Looking > at the specification for this feature, there doesn't seem to be much > interdependence between these APIs and the rest of WebCore. For > example, there's nothing that couples with dom, css, or rendering. > > Would it make sense to try building this feature as a self-contained > module? For example, you could imagine the following dependency > diagram: > > WebKit -----> WebP2P > | | > | \/ > +------------> WebCore > > Ideally, WebCore would have some moderately well-defined interface for > these modules, much like the WebKit <--> WebCore interaction is > mediated by clients. Ideally, these modules would just describe > themselves using WebIDL and we could just generated bindings for them. > As another example, webaudio might also profit from such as design. > > Of course, splitting this feature off into its own module doesn't > remove all the costs of the new feature, but it would make it easier > to work on WebCore proper without having to deal with all the > complexities of every feature. > > Adam > > > On Fri, May 13, 2011 at 11:10 AM, Eric Seidel <e...@webkit.org> wrote: >> That sounds like about 8 features. >> Seems we should think about this in smaller chunks... >> On the surface "peer to peer video conferencing" does not seem like >> something appropriate to add to WebCore/WebKit. Just like "an API for >> reading my email" is out of scope for the project. (But certainly lots of >> people build such things on top of WebKit.) :) >> -eric >> On Fri, May 13, 2011 at 6:19 AM, Tony Gentilcore <to...@chromium.org> wrote: >>> >>> For those interested, the cover bug for this work is here: >>> https://bugs.webkit.org/show_bug.cgi?id=56459 >>> -Tony >>> >>> On Fri, May 13, 2011 at 8:27 AM, Adam Bergkvist >>> <adam.bergkv...@ericsson.com> wrote: >>>> >>>> I want to inform people on this list that we have been doing some early >>>> implementation work of the video conferencing and peer-to-peer >>>> communication >>>> chapter in the HTML spec >>>> (http://www.whatwg.org/specs/web-apps/current-work/multipage/dnd.html#video-conferencing-and-peer-to-peer-communication). >>>> This section of the spec is in an early stage and should be considered >>>> experimental, but as it becomes more understood, we intend to contribute to >>>> the WebKit implementation. Others are also (based on bugs reported) working >>>> on this. >>>> BR >>>> Adam >>>> _______________________________________________ >>>> webkit-dev mailing list >>>> webkit-dev@lists.webkit.org >>>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev >>> >>> >>> _______________________________________________ >>> webkit-dev mailing list >>> webkit-dev@lists.webkit.org >>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev >>> >> >> >> _______________________________________________ >> webkit-dev mailing list >> webkit-dev@lists.webkit.org >> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev >> >> > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > -- Tommy Widenflycht, Senior Software Engineer Google Sweden AB, Kungsbron 2, SE-11122 Stockholm, Sweden Org. nr. 556656-6880 This email may be confidential or privileged. If you received this communication by mistake, please don't forward it to anyone else, please erase all copies and attachments, and please let me know that it went to the wrong person. Thanks! And yes, I have to include this message in every outgoing email according to EU law. _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev