two questions:1) app cache won't be used with workers, right? or is the goal for XHR requests from workers go through app cache? That would be pretty difficult to do since for example a shared worker isn't associated with any particular renderer. 2) what is the 'context' used for? the requestorID is the ID of the RenderView, so we could add static methods that get a RenderView (or WebViewDelegate) given its id, similar to how we do things in the browser process for RenderViewHost. Why do you need the reference btw? Is there code I can look at?
On Mon, Mar 16, 2009 at 2:04 PM, Michael Nordman <[email protected]>wrote: > We're going to need some kind of reference to the 'context' for the app > cache impl too, i had been depending on the WebFrame ptr for this thusfar, > but that won't help us in workers. > > On Mon, Mar 16, 2009 at 2:01 PM, John Abd-El-Malek <[email protected]>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 < >> [email protected]> 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: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
