Componentize safe_browsing [1]: create component, move messages, constants and switches.

components/safe_browsing/common/safebrowsing_constants.cc

Index: components/safe_browsing/common/safebrowsing_constants.cc
diff --git a/components/safe_browsing/common/safebrowsing_constants.cc b/components/safe_browsing/common/safebrowsing_constants.cc
new file mode 100644
index 0000000000000000000000000000000000000000..543f725e964c14f23d7bb412dc433d0a4fbf71bd
--- /dev/null
+++ b/components/safe_browsing/common/safebrowsing_constants.cc
@@ -0,0 +1,12 @@
+// Copyright 2016 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 "components/safe_browsing/common/safebrowsing_constants.h"
+
+namespace safe_browsing {
+
+const base::FilePath::CharType kSafeBrowsingBaseFilename[] =
+    FILE_PATH_LITERAL("Safe Browsing");

[Nathan Parker, 2016/11/10 18:57:46]

This won't be needed by WebView directly.  If it's easier to move some of these
rather than disentangle them, that's probably ok, but it would be cleaner to
leave the embedder data (file paths, switches) in /chrome/. 

[timvolodine, 2016/11/18 14:07:11]

safe_browsing_service uses that constant, and we'll need to move that file to
component as well because safe_browsing_resource_throttle depends on it.

[Nathan Parker, 2016/11/18 17:30:03]

Digging into this, it's used by the SafeBrowisingServiceImpl (which I assume
does not need componentizing), but then also by the safe_browsing_cookie_store. 
The latter _may_ be used by the PingManager (which does need moving).  Some safe
browsing code that shares that safe_browsing_request_context doesn't set cookies
so it wouldn't need this, but we can tease that apart another time.  I think
this is fine.

+
+}  // namespace safe_browsing