Add the scheme chrome-distiller:// and hook up data source.

components/dom_distiller/content/dom_distiller_viewer_source.cc

+// Copyright 2014 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/dom_distiller/content/dom_distiller_viewer_source.h"
+
+#include <string>
+
+#include "base/memory/ref_counted_memory.h"
+#include "base/memory/scoped_ptr.h"
+#include "content/public/browser/render_frame_host.h"
+#include "content/public/browser/render_view_host.h"
+#include "content/public/common/url_constants.h"
+#include "net/url_request/url_request.h"
+#include "url/gurl.h"
+
+namespace dom_distiller {
+
+DomDistillerViewerSource::DomDistillerViewerSource() {}
+
+DomDistillerViewerSource::~DomDistillerViewerSource() {}
+
+std::string DomDistillerViewerSource::GetSource() const {
+  return chrome::kDomDistillerScheme;
+}
+
+void DomDistillerViewerSource::StartDataRequest(
+    const std::string& path,
+    int render_process_id,
+    int render_frame_id,
+    const content::URLDataSource::GotDataCallback& callback) {
+  content::RenderFrameHost* render_frame_host =
+      content::RenderFrameHost::FromID(render_process_id, render_frame_id);
+  DCHECK(render_frame_host);
+  content::RenderViewHost* render_view_host =
+      render_frame_host->GetRenderViewHost();
+  DCHECK(render_view_host);
+  CHECK_EQ(0, render_view_host->GetEnabledBindings());
+
+  std::string page_template = "Aloha!";
+  callback.Run(base::RefCountedString::TakeString(&page_template));
+};
+
+std::string DomDistillerViewerSource::GetMimeType(const std::string& path)
+    const {

[nasko, 2014/01/23 16:37:04]

style: const shouldn't be on its own line.

[nyquist, 2014/01/24 03:03:07]

This is being done by our clang-format I am afraid.

[jam, 2014/01/24 22:07:54]

seems like until clang-format is fixed, this should be fixed manually before
upload

[Nico, 2014/01/24 22:16:35]

How'd you format this?

clang-format is used widely google-internally by now, and most aspects of it
have been discussed at length. Most of its formatting discussions are
intentional by now, not by accident. This doesn't look terrible to me fwiw. If
this agrees with google style, do you think it's bad enough that clang-format
should make chromium style deviate from google style in this respect? In
general, I thought we try to keep chromium style relatively similar to google
style. (There are a few differences, but this seems really minor.)

[jam, 2014/01/24 22:29:25]

Oh, I was under the impression that clang-format sometimes does things that
don't confirm. I completely agree that we should follow all the parts of the
google style guide everywhere since not doing so is a slippery slope.

I had looked in the google style guide and it didn't say anything about this
particular case. by convention, I know we didn't start a line with "const {" or
"OVERRIDE;" in chrome.

I wonder in cases like this where the google style guide doesn't say one thing
or the other, should we just go with what clang-format says, even if it goes
against the conventions we've used?

+  return "text/html";
+}
+
+bool DomDistillerViewerSource::ShouldServiceRequest(
+    const net::URLRequest* request) const {
+  return request->url().SchemeIs(chrome::kDomDistillerScheme);
+}
+
+std::string DomDistillerViewerSource::GetContentSecurityPolicyFrameSrc() const {
+  return "frame-src none;";
+}
+
+}  // namespace dom_distiller