[Webkit-unassigned] [Bug 217554] New: [GPU Process] Introduce RemoteResourceCacheProxy to manage the resources in the GPU Process

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=217554

            Bug ID: 217554
           Summary: [GPU Process] Introduce RemoteResourceCacheProxy to
                    manage the resources in the GPU Process
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Layout and Rendering
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: sabouhallawa at apple.com
                CC: bfulgham at webkit.org, simon.fraser at apple.com,
                    zalan at apple.com

RemoteRenderingBackendProxy will own an instance of RemoteResourceCacheProxy. One type of these resources will be the RemoteImageBufferProxy. We can split the responsibilities of the remote rendering among these classes like this:

-- RemoteRenderingBackendProxy: is responsible for sending messages to and receiving messages from the RemoteRenderingBackend. It will delegate all the resource management to its RemoteResourceCacheProxy
-- RemoteResourceCacheProxy: is responsible for managing the remote resources including the actual life cycle of these resources.
-- RemoteImageBufferProxy: is responsible for the ImageBuffer functionalities taking into consideration it is a remote resource, i.e drawing is recorded in WebProcess and backend lives in the GPU Process.

This makes it easy to get rid of RemoteImageBufferMessageHandlerProxy because all it does is sending messages to WebProcess but we can simplify the interface of RemoteImageBufferProxy by removing it and moving sending the messages to RemoteRenderingBackendProxy.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20201010/6eff01d7/attachment.htm>