compositor-worker: Initialize CW machinery plumbing to compositor and fire CW rAF callbacks.

third_party/WebKit/Source/core/dom/CompositorProxyClient.cpp

Index: third_party/WebKit/Source/core/dom/CompositorProxyClient.cpp
diff --git a/third_party/WebKit/Source/core/dom/CompositorProxyClient.cpp b/third_party/WebKit/Source/core/dom/CompositorProxyClient.cpp
new file mode 100644
index 0000000000000000000000000000000000000000..eeef0915feaf40c1a9b9244e983ee73f2c6ab375
--- /dev/null
+++ b/third_party/WebKit/Source/core/dom/CompositorProxyClient.cpp
@@ -0,0 +1,28 @@
+// Copyright 2015 The Chromium Authors. All rights reserved.

[haraken, 2016/05/06 02:45:50]

2016

[flackr, 2016/05/06 18:15:07]

Done.

+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#include "core/dom/CompositorProxyClient.h"
+
+#include "platform/TraceEvent.h"
+
+namespace blink {
+
+CompositorProxyClient* CompositorProxyClient::from(WorkerClients* clients)
+{
+    TRACE_EVENT0("compositor-worker", "CompositorProxyClient::from");

[haraken, 2016/05/06 02:45:50]

Does this performance really matter? Supplement::from is just looking up a hash
map.

[flackr, 2016/05/06 18:15:07]

Agreed, this should be fine. Removed.

+    return static_cast<CompositorProxyClient*>(Supplement<WorkerClients>::from(clients, supplementName()));
+}
+
+const char* CompositorProxyClient::supplementName()
+{
+    return "CompositorProxyClient";
+}
+
+void provideCompositorProxyClientTo(WorkerClients* clients, CompositorProxyClient* client)
+{
+    TRACE_EVENT0("compositor-worker", "provideCompositorProxyClientTo");

[haraken, 2016/05/06 02:45:50]

Ditto. This should happen only once, so it wouldn't be performance-sensitive.

It looks like this CL is adding a bit too many TRACE_EVENTs.

[flackr, 2016/05/06 18:15:07]

Removed.

+    clients->provideSupplement(CompositorProxyClient::supplementName(), client);
+}
+
+} // namespace blink