Comment #5 on issue 8073 by [email protected]: Need process singleton implementation http://code.google.com/p/chromium/issues/detail?id=8073
I believe the right way to implement this is: - make the process singleton objects take in a MessageLoopForIO* (see base/message_loop.h), which allows you to call ->WatchFileDescriptor() on POSIX - have the chrome process, on startup, pass in its MessageLoopForIO::current() In general, base/message_loop.h was the class you need, I think. (I believe socket watching should happen on the "IO" Chromium thread; I'm not certain if MessageLoopForIO::current() gives you that if you call it from the main browser thread, but if not we can discuss that detail at review-time.) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
