The only place that calls it in the browser process is
BrowserAccessbilityManager, which I'm guessing isn't critical for the ports
(it's actually disabled by default on our shipping builds).
success = members->render_widget_host_->process()->channel()->
SendWithTimeout(msg, kAccessibilityMessageTimeOut);
process() returns a RenderProcessHost, whose channel() returns a SyncChannel
which has the SendWithTimeout.
On Thu, Mar 12, 2009 at 11:04 AM, Avi Drissman <[email protected]> wrote:
> OK, so there's this nifty SendWithTimeout on SyncChannel. Awesome. And
> RenderViewHost just has to call it, just like it calls Send() today for
> other calls.
>
> This is where things are falling apart for me.
>
> For Send(), RenderViewHost calls (via RWH) its Send(), which calls
> RenderProcessHost's Send(), which ends up in BrowserRenderProcessHost, which
> has a SyncChannel. But the intermediate steps are a blur. RenderProcessHost
> doesn't actually have Send(), but apparently inherits it from
> IPC::Channel::Sender, and as far as I can tell there is no such thing.
>
> I'm obviously missing something. Thoughts?
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: [email protected]
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
