[chromium-dev] Re: rev 11763 removes frame pointer from ResourceRequest

2009-03-17 Thread Marshall Greenblatt
I would be in favor of #2 -- retrieving the WebViewDelegate associated with the requestorID. On Mon, Mar 16, 2009 at 5:25 PM, John Abd-El-Malek j...@chromium.org wrote: two questions:1) app cache won't be used with workers, right? or is the goal for XHR requests from workers go through app

[chromium-dev] Re: rev 11763 removes frame pointer from ResourceRequest

2009-03-16 Thread Marshall Greenblatt
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

[chromium-dev] Re: rev 11763 removes frame pointer from ResourceRequest

2009-03-16 Thread Brett Wilson
On Mon, Mar 16, 2009 at 4:25 PM, Marshall Greenblatt magreenbl...@gmail.com wrote: 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