Remove ssl_host_state.h dependency from chrome.

I suspect there'll be a few objects that hang off BrowserContext/ResourceContext which are per profile that we don't want chrome to know about or even to create. For now, I did a one-off by manually keeping a map and deleting it when the BrowserContext goes away. If we hit others, we can generalize this into a template, perhaps like RenderViewHostObserverTracker.

BUG=98716
Review URL: https://chromiumcodereview.appspot.com/9384029

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@121706 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 23 insertions, 0 deletions

diff --git a/content/public/browser/browser_context.cc b/content/public/browser/browser_context.cc
new file mode 100644
index 0000000..c3f931e
--- /dev/null
+++ b/content/public/browser/browser_context.cc
@@ -0,0 +1,23 @@
+// Copyright (c) 2012 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#include "content/public/browser/browser_context.h"
+
+#include "base/logging.h"
+#include "content/public/browser/browser_thread.h"
+#include "content/public/browser/notification_details.h"
+#include "content/public/browser/notification_service.h"
+#include "content/public/browser/notification_source.h"
+#include "content/public/browser/notification_types.h"
+
+namespace content {
+
+BrowserContext::~BrowserContext() {
+  NotificationService::current()->Notify(
+      content::NOTIFICATION_BROWSER_CONTEXT_DESTRUCTION,
+      content::Source<BrowserContext>(this),
+      content::NotificationService::NoDetails());
+}
+
+}  // namespace content