Add more of the server-side plumbing for extension APIs. Also

chrome/browser/renderer_host/browser_render_process_host.cc

Index: chrome/browser/renderer_host/browser_render_process_host.cc
diff --git a/chrome/browser/renderer_host/browser_render_process_host.cc b/chrome/browser/renderer_host/browser_render_process_host.cc
index c694fdddbf7469d8dcbf7078bfd062e0c627679f..81f391514c53a74551aff69350899efc51896f83 100644
--- a/chrome/browser/renderer_host/browser_render_process_host.cc
+++ b/chrome/browser/renderer_host/browser_render_process_host.cc
@@ -345,6 +345,7 @@ bool BrowserRenderProcessHost::Init() {
 
   InitVisitedLinks();
   InitUserScripts();
+  InitExtensions();
 
   if (max_page_id_ != -1)
     channel_->Send(new ViewMsg_SetNextPageID(max_page_id_ + 1));
@@ -447,6 +448,14 @@ void BrowserRenderProcessHost::InitUserScripts() {
   SendUserScriptsUpdate(user_script_master->GetSharedMemory());
 }
 
+void BrowserRenderProcessHost::InitExtensions() {
+  // TODO(aa): Should only bother sending these function names if this is an
+  // extension process.
+  std::vector<std::string> function_names;
+  ExtensionFunctionDispatcher::GetAllFunctionNames(&function_names);
+  Send(new ViewMsg_Extension_SetFunctionNames(function_names));
+}
+
 void BrowserRenderProcessHost::SendUserScriptsUpdate(
     base::SharedMemory *shared_memory) {
   base::SharedMemoryHandle handle_for_process;