Support sharing of ContentMain and BrowserMain code with embedded use cases.

content/public/browser/browser_main_parts.h

Index: content/public/browser/browser_main_parts.h
===================================================================
--- content/public/browser/browser_main_parts.h	(revision 117304)
+++ content/public/browser/browser_main_parts.h	(working copy)
@@ -10,6 +10,8 @@
 #include "content/common/content_export.h"
 #include "content/public/browser/browser_thread.h"
 
+class MessageLoop;
+
 namespace content {
 
 // This class contains different "stages" to be executed by |BrowserMain()|,
@@ -60,6 +62,10 @@
 
   virtual void PreMainMessageLoopStart() = 0;
 
+  // Return the main message loop object or NULL to use the default message
+  // loop object.
+  virtual MessageLoop* GetMainMessageLoop() = 0;

[jam, 2012/01/12 18:07:18]

I'm not sure I understand this. I thought CEF/Awesomium wanted to just call
everything before running the message loop, and then they'll pump whenever they
want, and then when they want to quit they'll call everything currently after
running the ML? In that case, you wouldn't want to give a custom ML?

+
   virtual void PostMainMessageLoopStart() = 0;
 
   // Allows an embedder to do any extra toolkit initialization.