[wip] Profile: Sketch of a creation system.

chrome/browser/profiles/profile_keyed_service_factory.h

Index: chrome/browser/profiles/profile_keyed_service_factory.h
diff --git a/chrome/browser/profiles/profile_keyed_service_factory.h b/chrome/browser/profiles/profile_keyed_service_factory.h
index f805db7f0d05c38f23a7bab802eb18ab52666ed0..8efd3c31f1df0403f7f1e807b0af7d73e9664314 100644
--- a/chrome/browser/profiles/profile_keyed_service_factory.h
+++ b/chrome/browser/profiles/profile_keyed_service_factory.h
@@ -75,6 +75,18 @@ class ProfileKeyedServiceFactory {
   virtual bool ServiceRedirectedInIncognito();
   virtual bool ServiceHasOwnInstanceInIncognito();
 
+  // By default, we create instances of a service lazily and wait until
+  // GetForProfile() is called on our subclass. Some service need to be created
+  // as soon as the Profile has been brought up.
+  virtual bool ServiceIsCreatedWithProfile();

[Miranda Callahan, 2011/07/01 15:20:24]

I wonder if we really need this function; won't any factory that appears in the
AssertFactoriesBuilt method be one of the ones for which
ServiceIsCreatedWithProfile will return true?

+
+  // By default, TestingProfiles will be treated like normal profiles. You can
+  // override this so that by default, the service associated with the
+  // TestingProfile is NULL. (This is just a shortcut around
+  // SetTestingFactory() to make sure our profile's don't directly refer to the
+  // services they use.)
+  virtual bool ServiceIsNULLWhileTesting();
+
   // A helper object actually listens for notifications about Profile
   // destruction, calculates the order in which things are destroyed and then
   // does a two pass shutdown.