1345789 - [Mortar] [Windows] setup an IPC between parent process and plugin process

Status: RESOLVED INVALID

(Core :: Printing: Output, enhancement)

Comment 1

[Farmer Tseng[:fatseng](inactive)]

To utilize pdfium.dll which runs in the plugin process converts PDF to EMF.
Therefore, I would like to establish an IPC between Chrome and plugin process.

Comment 2

[Louis Chang [:louis]]

Attachment: [WIP] Test ipc between chrome and plugin process

The patch is to test the feasibility of the communication between chrome process and plugin process based on new jsplugin architecture.

Comment 3

[Louis Chang [:louis]]

Attachment: [WIP] Test ipc between chrome and plugin process with new protocol

In the patch, I constructs an ipc between chrome and jsplugin process by creating new protocol. (But we are suppose to construct an ipc between chrome and plugin process.)

It seems that there are still some bridges stuffs need to be done to support ipc communication between chrome process and plugin process. But the keyword "bridges" is deprecated in latest ipc protocol. So I decide to work on the patch until patches in bug 1344942 are landed. Or there is updated information of that we are feasible to get the |PPAPIJSPluginParent| directly in chrome process.

Comment 4

[Louis Chang [:louis]]

Hi Peter,

Do you have any concern or suggestion of getting PPAPIJSPluginParent in Chrome process for printing PDF as discussion in weekly meeting last week? Or it is better to create a new protocol for printing PDF?

Feel free to leave any comment. Thanks.

Comment 5

[Louis Chang [:louis]]

Update:
After discussion with kanru and farmer, we come out two solutions,
1. Use existing PPAPIJSPlugin ipc protocol and add printing PDF related functions on the protocol. There is only one ipc is created for multiple tabs, so in order to distinguish which tab is printing now, we have to pass an id through every ipc call also pass promise in case of two tabs print simultaneously.
2. Implement new protocol managed by PPAPIJSPlugin, and create ipc for each tab.

We will first implement the first version, then improve to the second version later.

Comment 6

[Farmer Tseng[:fatseng](inactive)]

Attachment: [WIP] Retrieve plugin parent

Comment 7

[Farmer Tseng[:fatseng](inactive)]

Attachment: [WIP} Print EMF

Comment 8

[Farmer Tseng[:fatseng](inactive)]

(In reply to Farmer Tseng[:fatseng] from comment #6)
> Created attachment 8864012 [details] [diff] [review]
> [WIP] Retrieve plugin parent

This patch is based on attachment 8850404 [details] [diff] [review] to implement a way that retrieves correct PPAPIJSPlugParent.
nsDeviceContextSpecWin utilizes PPAPIJSPlugParent to communicate with PPAPIJSPlugChild.

Comment 9

[Farmer Tseng[:fatseng](inactive)]

(In reply to Farmer Tseng[:fatseng] from comment #7)
> Created attachment 8864026 [details] [diff] [review]
> [WIP} Print EMF

This patch coverts PDF to EMF in the child process.
Parent process gets EMF from the child and draws it on printer DC page by page.

Comment 10

[Louis Chang [:louis]]

Attachment: Prototype of handling multiple tabs printing

Comment 11

[Farmer Tseng[:fatseng](inactive)]

Attachment: [WIP} Print EMF

Prototype of printing EMF