Oops...sorry for the misinformation...should have double checked before I said anything. :-)
On Mon, Aug 24, 2009 at 1:26 PM, John Abd-El-Malek <j...@chromium.org> wrote: > > > On Mon, Aug 24, 2009 at 1:06 PM, Brett Wilson <bre...@chromium.org> wrote: > >> >> On Mon, Aug 24, 2009 at 12:49 PM, hap 497<hap...@gmail.com> wrote: >> > Thanks. But the picture in the document shows there is only 1 >> > ResourceDispatcherHost and there are 2 Renderer Processes: >> > >> > >> http://dev.chromium.org/developers/design-documents/multi-process-architecture >> > And the ResourceDispatcherHost has access to both Channels for each >> Renderer >> > Process. >> >> Information about each request including the originating renderer is >> tacked onto each URLRequest in the form of "ExtraRequestInfo." See one >> of the functions in there such as >> ResourceDispatcherHost::OnResponseCompleted for how this is retrieved. >> > > Right, information such as renderer process id is available, but there are > no pointers to the ResourceMessageFilter in there. Using the process id, > you could get to the RenderProcessHost (but only on the UI thread) and from > there to the RMF. > > >> >> Brett >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
