Hi,

What we will do:

1.       Establish ChannelMojo connection between BP< --- >EP, to replace old 
IPC Channel.  ChannelMojo impl in Chromium is still ongoing and unstable,  
we’re keeping an eye on it.

2.       Replace old IPC messages with Mojo IDL. Eventually we want to do this 
for all Crosswalk IPC messages, including IPC of BP< -- >RP, RP< -- >EP, EP< -- 
>BP. This work needs to figure out use case for every specific message and give 
deliberate design which maybe change current logic greatly. We’ll do this work 
step by step.

BP --- > Browser Process
RP --- > Render Process
EP --- > Extension Process

Thanks.

BR,
Han Leon
From: Long, Xiang
Sent: Wednesday, March 18, 2015 3:24 PM
To: Han, Leon; [email protected]
Subject: Re: [Crosswalk-dev] Intent to Implement: Replace Chromium IPC with 
Mojo IPC

Would you please clarify what will changed in more details?
E.g., will current extension implementation process still valid? Are we also 
transferring JS IPC wrapper to Mojo IDL?

Thanks!
Xiang
On 2015年03月06日 14:21, Han, Leon wrote:
Description:
Google is planning to replace all Chromium IPC with Mojo IPC, we should also 
start to do this work for Crosswalk.
Google is doing:
1.       Implement ChannelMojo to transfer IPC messages.
2.       Transform features based on Chromium IPC into Mojo services.

Affected component: all

Related feature: XWALK-3675

Target release: future release

Implementation details:
1.       Rework to enable employing ChannelMojo. (Suppose at least need be done 
for Crosswalk Extensions)
2.       Transform Crosswalk features based on Chromium IPC into Mojo services. 
(Including IPCs between Browser/Render/Extension processes)

BR,
Han Leon





_______________________________________________

Crosswalk-dev mailing list

[email protected]<mailto:[email protected]>

https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev

_______________________________________________
Crosswalk-dev mailing list
[email protected]
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev

Reply via email to