Added FrameFuture class

content/public/browser/android/synchronous_compositor.cc

 // Copyright 2016 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/public/browser/android/synchronous_compositor.h"
 
 #include <utility>
 
 #include "cc/output/compositor_frame.h"
 
 namespace content {
 
 SynchronousCompositor::Frame::Frame() : output_surface_id(0u) {}
 
 SynchronousCompositor::Frame::~Frame() {}
 
 SynchronousCompositor::Frame::Frame(Frame&& rhs)
     : output_surface_id(rhs.output_surface_id), frame(std::move(rhs.frame)) {}
 
+SynchronousCompositor::FrameFuture::FrameFuture()
+    : waitable_event_(base::WaitableEvent::ResetPolicy::AUTOMATIC,

[boliu, 2016/09/16 16:26:12]

should be manual

[ojars, 2016/09/19 22:02:37]

Done.

+                      base::WaitableEvent::InitialState::NOT_SIGNALED) {}
+
+SynchronousCompositor::FrameFuture::~FrameFuture() {}
+
+void SynchronousCompositor::FrameFuture::setFrame(
+    std::unique_ptr<content::SynchronousCompositor::Frame> frame) {
+  frame_ = std::move(frame);
+  waitable_event_.Signal();
+}
+
+content::SynchronousCompositor::Frame*
+SynchronousCompositor::FrameFuture::getFrame() {
+  waitable_event_.Wait();

[boliu, 2016/09/16 16:26:12]

All the waitable_event calls are super expensive. We shouldn't repeat the just
because all over the place.

Hmm, this is actually an interesting exercise how this class should behave. I
think we should talk about this in person.

+  return frame_.get();
+}
+
+bool SynchronousCompositor::FrameFuture::hasFrame() {
+  return waitable_event_.IsSignaled();
+}
+
 SynchronousCompositor::Frame& SynchronousCompositor::Frame::operator=(
     Frame&& rhs) {
   output_surface_id = rhs.output_surface_id;
   frame = std::move(rhs.frame);
   return *this;
 }
 
 }  // namespace content