We don't support multi-process extension. Instead, multi-threaded extension mechanism is used. On Android, there is no shared runtime model, no multi process. This is a really different story compared to Tizen because many different behaviors and restrictions from Android. I think Caio can share more details about in-process extension mechanism. Thanks for your question, Gustavo.
Yongsheng > -----Original Message----- > From: Barbieri, Gustavo > Sent: Thursday, October 31, 2013 2:11 AM > To: Zhu, Yongsheng > Cc: [email protected]; Gao, Chun > Subject: Re: [Crosswalk-dev] Crosswalk Java extension mechanism on Android > > On Wed, Oct 30, 2013 at 05:22:43AM +0000, Zhu, Yongsheng wrote: > > Hi, All > > I'm glad to announce that the Java extension on Android is basically > > ready for usages of both internal and external extensions. That's to > > say, crosswalk developers and web developers can develop SysApps APIs > > and external extensions combined with their web apps together on > > Android. Thanks to Gao Chun, Huo Halton and Wu Donna to help me set up > > this mechanism. Thanks to the guys from native extension mechanism as > > well. > > > > * Features: > > Sit on top of native extension mechanism but de-coupled. No changes > > to JavaScript code stub. Pure Java implementation since Android > > only provides Java system APIs. > > Support multiple instances of extensions. > > > Support internal extension. Now extensions like WiDi and Device > > capabilities have already based on internal extensions and work > > well. > > External extensions are supported on both shared mode and embedded > mode. > > * Why: > > > > Current native extension mechanism only works for C++. However, all > > Android APIs are exposed as Java language. It's more convenient and > > easy to develop and maintain extension implementations based on > > Android Java extension system. > > * How to develop extensions: > > For external extensions, please see the documentation > > here<https://github.com/crosswalk-project/crosswalk-website/wiki/Writi > > ng-a-Crosswalk-Java-Extension-on-Android>. More automatic scripts to > > aid web developers are needed. Welcome to your comments. JamesK, could > > you please help review it and might migrate it to crosswalk-project.org in > future? > > For internal extensions, please follow up the code of WiDi and Device > > capabilities. Easy to use. > > * Limitations: > > Currently if a Java implementation of extension needs additional > > Android permissions, we don't support them in crosswalk tools. But > > we'll add the support soon. > > * Open: > > We'd like to migrate the design doc into google doc. Any > > guideline or BKM? > > Very good Yongsheng, one question: how does this behave in the safety and > multi-process? Does it follow the same as Tizen where we have isolated BP, RP > and EP? Does it already create one EP per RP that uses extensions or is it one > single EP shared among all RP? (I'm not sure you're supporting shared runtime > model, then some points may be moot) > > -- > Gustavo Sverzut Barbieri > Intel Open source Technology Center _______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
