Remove Gears from Chrome

chrome/common/render_messages_params.h

 // Copyright (c) 2010 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.
 
 #ifndef CHROME_COMMON_RENDER_MESSAGES_PARAMS_H_
 #define CHROME_COMMON_RENDER_MESSAGES_PARAMS_H_
 #pragma once
 
 #include <string>
 #include <vector>
@@ skipping 466 matching lines @@
   // Optional upload data (may be null).
   scoped_refptr<net::UploadData> upload_data;
 
   bool download_to_file;
 
   // True if the request was user initiated.
   bool has_user_gesture;
 
   // The following two members are specified if the request is initiated by
   // a plugin like Gears.
+  // TODO(aa): Can these be removed now? Unclear if they are being used.

[evanm, 2011/02/25 21:47:13]

Why not?  I guess we can find it later by grepping again for Gears, but we
shouldn't close the Gears bug until we get all of these...

[Aaron Boodman, 2011/02/25 22:29:28]

It seemed like maybe external automation clients could have been relying on it,
but I think I misread the code. Removed.

 
   // Contains the id of the host renderer.
   int host_renderer_id;
 
   // Contains the id of the host render view.
   int host_render_view_id;
 };
 
 // Parameters for a render request.
 struct ViewMsg_Print_Params {
@@ skipping 706 matching lines @@
 struct ParamTraits<ViewHostMsg_MalwareDOMDetails_Node> {
   typedef ViewHostMsg_MalwareDOMDetails_Node param_type;
   static void Write(Message* m, const param_type& p);
   static bool Read(const Message* m, void** iter, param_type* p);
   static void Log(const param_type& p, std::string* l);
 };
 
 }  // namespace IPC
 
 #endif  // CHROME_COMMON_RENDER_MESSAGES_PARAMS_H_