mojo: Use ContentHandlers to bundle multiple Applications into a module.

mojo/runner/context.cc

 // Copyright 2013 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 "mojo/runner/context.h"
 
 #include <vector>
 
 #include "base/bind.h"
 #include "base/command_line.h"
@@ skipping 92 matching lines @@
   return true;
 }
 
 void InitContentHandlers(shell::ApplicationManager* manager,
                          const base::CommandLine& command_line) {
   // Default content handlers.
   manager->RegisterContentHandler("application/pdf", GURL("mojo:pdf_viewer"));
   manager->RegisterContentHandler("image/png", GURL("mojo:png_viewer"));
   manager->RegisterContentHandler("text/html", GURL("mojo:html_viewer"));
 
+  // TODO(erg): We should probably handle this differently; these could be
+  // autogenerated from package manifests.
+  manager->RegisterApplicationPackageRedirect(GURL("mojo:clipboard"),
+                                              GURL("mojo:core_services"));
+
   // Command-line-specified content handlers.
   std::string handlers_spec =
       command_line.GetSwitchValueASCII(switches::kContentHandlers);
   if (handlers_spec.empty())
     return;
 
 #if defined(OS_ANDROID)
   // TODO(eseidel): On Android we pass command line arguments is via the
   // 'parameters' key on the intent, which we specify during 'am shell start'
   // via --esa, however that expects comma-separated values and says:
@@ skipping 194 matching lines @@
     if (app_urls_.empty() && base::MessageLoop::current()->is_running()) {
       DCHECK_EQ(base::MessageLoop::current()->task_runner(),
                 task_runners_->shell_runner());
       base::MessageLoop::current()->Quit();
     }
   }
 }
 
 }  // namespace runner
 }  // namespace mojo