GPU client side changes for GpuMemoryBuffers

gpu/command_buffer/common/image_buffer_manager.h

+// Copyright (c) 2013 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 GPU_COMMAND_BUFFER_COMMON_IMAGE_BUFFER_MANAGER_H_
+#define GPU_COMMAND_BUFFER_COMMON_IMAGE_BUFFER_MANAGER_H_
+
+#include "base/basictypes.h"
+
+namespace gpu {
+namespace gles2 {
+
+// TODO(kaanb): Is GLES2_IMPL_EXPORT the right macro to use?
+class ImageManagerProxy {

[joth, 2013/05/03 00:49:37]

can we simplify this?
- remove this interface
- no changes needed in ImageManager (service side)
- make GpuMemBufferFactory into a virtual base class
- have WC3D in-process provide a specialized sub-class of GpuMemBufferFactory
that knows how to poke GLImage::CreateFromGpuMemBuffer() and
ImageManager->AddImage() to make the buffer available to the service side
- GLES2 implementation would be exactly as in this patchset: passed in a
GpuMemBufferFactory instance and rely on that to do the service side mapping of
GpuMemBuffer -> GL image.

What do others think?

+ public:
+  virtual ~ImageManagerProxy() {}
+  virtual void AddImageBuffer(void* buffer, int width, int height,
+                              int image_id) = 0;
+};
+
+}  // namespace gles2
+}  // namespace gpu
+
+#endif  // GPU_COMMAND_BUFFER_COMMON_IMAGE_BUFFER_MANAGER_H_