Gears File Drag Drop

r24899 now keys the child security policy database based on 
renderer id, rather than renderer process id. Update gears 
drag drop to use the renderer id for the file policy access 
checks. 

This is a clone for submission of of noel's original CL
http://codereview.chromium.org/195079

BUG=7995


Review URL: http://codereview.chromium.org/196145

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

1 files changed, 8 insertions, 3 deletions

diff --git a/chrome/plugin/plugin_channel.h b/chrome/plugin/plugin_channel.h
index 58e711f..5e512f3 100644
--- a/chrome/plugin/plugin_channel.h
+++ b/chrome/plugin/plugin_channel.h
@@ -1,4 +1,4 @@
-// Copyright (c) 2006-2008 The Chromium Authors. All rights reserved.
+// Copyright (c) 2009 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.
 
@@ -16,8 +16,8 @@
 class PluginChannel : public PluginChannelBase {
  public:
   // Get a new PluginChannel object for the current process to talk to the
-  // given rendeer process. The renderer ID is an opaque unique ID generated by
-  // the browser.
+  // given renderer process. The renderer ID is an opaque unique ID generated
+  // by the browser.
   //
   // POSIX only: If |channel_fd| > 0, use that file descriptor for the
   // channel socket.
@@ -30,6 +30,8 @@ class PluginChannel : public PluginChannelBase {
   virtual void OnMessageReceived(const IPC::Message& message);
 
   base::ProcessHandle renderer_handle() const { return renderer_handle_; }
+  int renderer_id() { return renderer_id_; }
+
   int GenerateRouteID();
 
 #if defined(OS_POSIX)
@@ -76,6 +78,9 @@ class PluginChannel : public PluginChannelBase {
   // Handle to the renderer process who is on the other side of the channel.
   base::ProcessHandle renderer_handle_;
 
+  // The id of the renderer who is on the other side of the channel.
+  int renderer_id_;
+
 #if defined(OS_POSIX)
   // FD for the renderer end of the pipe. It is stored until we send it over
   // IPC after which it is cleared. It will be closed by the IPC mechanism.