Add IPC messages to transfer compositor protos

content/browser/renderer_host/render_widget_host_impl.cc

 // Copyright (c) 2012 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 "content/browser/renderer_host/render_widget_host_impl.h"
 
 #include <math.h>
 #include <set>
 #include <utility>
 
@@ skipping 455 matching lines @@
 #if defined(OS_WIN)
     IPC_MESSAGE_HANDLER(ViewHostMsg_WindowlessPluginDummyWindowCreated,
                         OnWindowlessPluginDummyWindowCreated)
     IPC_MESSAGE_HANDLER(ViewHostMsg_WindowlessPluginDummyWindowDestroyed,
                         OnWindowlessPluginDummyWindowDestroyed)
 #endif
     IPC_MESSAGE_HANDLER(InputHostMsg_ImeCompositionRangeChanged,
                         OnImeCompositionRangeChanged)
     IPC_MESSAGE_HANDLER(ViewHostMsg_DidFirstPaintAfterLoad,
                         OnFirstPaintAfterLoad)
+    IPC_MESSAGE_HANDLER(ViewHostMsg_SendCompositorProto,

[no sievers, 2015/11/14 00:13:43]

nit: it's slightly contradictory between Send/OnHandle. would the notion of
'ViewHostMsg_ForwardCompositorProto/OnForwardCompositorProto' make sense? or
'relay' or something?

[David Trainor- moved to gerrit, 2015/11/16 04:33:58]

Done.

+                        OnHandleCompositorProto)
     IPC_MESSAGE_UNHANDLED(handled = false)
   IPC_END_MESSAGE_MAP()
 
   if (!handled && input_router_ && input_router_->OnMessageReceived(msg))
     return true;
 
   if (!handled && view_ && view_->OnMessageReceived(msg))
     return true;
 
   return handled;
@@ skipping 461 matching lines @@
 }
 
 void RenderWidgetHostImpl::OnFirstPaintAfterLoad() {
   if (new_content_rendering_timeout_->IsRunning()) {
     new_content_rendering_timeout_->Stop();
   } else {
     received_paint_after_load_ = true;
   }
 }
 
+void RenderWidgetHostImpl::OnHandleCompositorProto(
+    const std::vector<char>& proto) {
+  if (delegate_)
+    delegate_->HandleCompositorProto(this, proto);
+}
+
 void RenderWidgetHostImpl::ForwardMouseEvent(const WebMouseEvent& mouse_event) {
   ForwardMouseEventWithLatencyInfo(mouse_event, ui::LatencyInfo());
 }
 
 void RenderWidgetHostImpl::ForwardMouseEventWithLatencyInfo(
       const blink::WebMouseEvent& mouse_event,
       const ui::LatencyInfo& ui_latency) {
   TRACE_EVENT2("input", "RenderWidgetHostImpl::ForwardMouseEvent",
                "x", mouse_event.x, "y", mouse_event.y);
 
@@ skipping 279 matching lines @@
 }
 
 bool RenderWidgetHostImpl::GetScreenColorProfile(
     std::vector<char>* color_profile) {
   DCHECK(color_profile->empty());
   if (view_)
     return view_->GetScreenColorProfile(color_profile);
   return false;
 }
 
+void RenderWidgetHostImpl::HandleCompositorProto(

[no sievers, 2015/11/14 00:13:43]

oops, now i'm even more confused, 'Handle' overload :)
this goes into the other direction... so hhmm.. how about some notion of
'incoming' vs. 'outgoing' to differentiate?

[David Trainor- moved to gerrit, 2015/11/16 04:33:58]

Yeah this is weird.  I made it HandleCompositorProto for incoming and
ForwardCompositorProto for outgoing (after reading the previous comment).  I can
make this explicitly incoming/outgoing if you want though :).

+    const std::vector<char>& proto) {
+  DCHECK(!proto.empty());
+  Send(new ViewMsg_HandleCompositorProto(GetRoutingID(), proto));
+}
+
 void RenderWidgetHostImpl::NotifyScreenInfoChanged() {
   color_profile_out_of_date_ = true;
 
   if (delegate_)
     delegate_->ScreenInfoChanged();
 
   // The resize message (which may not happen immediately) will carry with it
   // the screen info as well as the new size (if the screen has changed scale
   // factor).
   WasResized();
@@ skipping 940 matching lines @@
 }
 
 #if defined(OS_WIN)
 gfx::NativeViewAccessible
     RenderWidgetHostImpl::GetParentNativeViewAccessible() {
   return delegate_ ? delegate_->GetParentNativeViewAccessible() : NULL;
 }
 #endif
 
 }  // namespace content