Explaination on cross-process data sharing model

49 views
Skip to first unread message

MinhHoang To

unread,
Aug 25, 2015, 10:45:41 PM8/25/15
to Chromium-dev
AFAIK, the main browser process handles all network communications.

Consider the case renderer process need to fetch CSS, JavaScript or Image resource from Internet, it sends IPC ResourceMessage to the main process, the later then makes HTTP request to fetch resource. So, how those resource could be accessible from WebKit code in renderer process?

Eric Roman

unread,
Aug 31, 2015, 2:27:05 PM8/31/15
to hoang...@gmail.com, Chromium-dev

On Tue, Aug 25, 2015 at 7:45 PM, MinhHoang To <hoang...@gmail.com> wrote:
AFAIK, the main browser process handles all network communications.

Consider the case renderer process need to fetch CSS, JavaScript or Image resource from Internet, it sends IPC ResourceMessage to the main process, the later then makes HTTP request to fetch resource. So, how those resource could be accessible from WebKit code in renderer process?

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

Eric Roman

unread,
Aug 31, 2015, 2:28:32 PM8/31/15
to hoang...@gmail.com, Chromium-dev
Actually meant to send this link instead of the displaying webpage one:

MinhHoang To

unread,
Sep 1, 2015, 4:04:08 AM9/1/15
to Chromium-dev, hoang...@gmail.com
@Eric:

Your link is about how 'renderer' process ask 'main' process to do network task.

My question is about the data sharing model in Chromium that make the content fetched by 'main' process (html, javascript, css, images,...) available to that 'renderer' process.

Primiano Tucci

unread,
Sep 1, 2015, 2:05:29 PM9/1/15
to MinhHoang To, Chromium-dev
On Tue, Sep 1, 2015 at 9:04 AM, MinhHoang To <hoang...@gmail.com> wrote:
My question is about the data sharing model in Chromium that make the content fetched by 'main' process (html, javascript, css, images,...) available to that 'renderer' process.

Which is, very succinctly, indicated in that doc.
If you take a look  at ResourceDispatcherHostimpl, which in turn uses Sync/AsyncResourceHandler you will see the actual shared memory buffers being transferred via IPC in the browser->renderer direction.
If you follow the IPC messages you will see how they are consumed in the renderer side.
Reply all
Reply to author
Forward
0 new messages