yeah, I've actually been doing what Evan mentioned, but I'm running into the lifetime issues (as he points out). That's actually what prompted this post. Sounds like I should step back and reconsider the design. Thanks for the responses guys!
On May 25, 3:48 pm, Aaron Boodman <[email protected]> wrote: > On Mon, May 25, 2009 at 3:44 PM, Evan Martin <[email protected]> wrote: > > If you're trying to catch a notification that needs to get to a worker > > thread, a pattern we use elsewhere is to have an object that lives on > > the UI thread that gets the notification then makes an async call over > > to the worker thread. You have to be careful about the relative > > lifetimes of the objects involved, but it can be done. Take a look at > > the greasemonkey master class (I think?) or maybe the FileWatcher > > class. > > ChromeURLRequestContext is another good example of this, I think. > > - a --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
