On Tue, Apr 28, 2009 at 5:27 PM, Michael Nordman <[email protected]>wrote:
> > In some sense we do have separate process in which to run sandboxed > > 'backend' code relevant to multiple renders if the need arises... the > > worker process. > The way you stated this is a bit odd, but on the surface I guess this could be solved via special "shared workers" that ran WebKit code instead of javascript. That said, this means a lot of extra processes (for now, shared workers are each in their own process), this blocks localStorage on that, and actually makes the design more complicated. This might be worth exploring at some point, but not now. --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
