My needs in this case are related to the Chromium Embedded Framework (CEF). The code currently works as follows:
1. Retrieve our custom WebViewDelegate instance pointer via the WebFrame pointer passed to ResourceLoaderBridge::Create(). 2. Pass a CefBrowser pointer retrieved from our custom WebViewDelegate instance into the new ResourceLoaderBridgeImpl. 3. During the execution of RequestProxy::AsyncStart() access callbacks provided by CefHandler (retrieved from CefBrowser) to optionally provide alternate data streams, transparently redirect requests, etc. You can view the source code here: http://code.google.com/p/chromiumembedded/source/browse/trunk/libcef/browser_resource_loader_bridge.cc Does chromium currently maintain the relationship between the 'routing_id' parameter and the WebFrame pointer somewhere within the code base, or will we need to add this mapping capability ourselves? Or is there perhaps a completely different approach that CEF should be using to provide this capability? Thanks, Marshall On Mon, Mar 16, 2009 at 4:01 PM, John Abd-El-Malek <j...@chromium.org> wrote: > The reason I did it was because in the worker process, there's no frame. > Why/where do you need it? > > > On Mon, Mar 16, 2009 at 1:46 PM, Marshall Greenblatt < > magreenbl...@gmail.com> wrote: > >> Hi John, >> >> Rev 11763 removes the WebFrame pointer that was previously passed to >> ResourceLoaderBridge::Create() in simple_resource_loader_bridge.cc. How can >> I use the new 'routing_id' parameter to retrieve the WebFrame pointer, if >> any, that originated the request? >> >> Thanks, >> Marshall >> > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
