[Webkit-unassigned] [Bug 24054] Implement two separate proxy classes in order to split WorkerMessagingProxy.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Feb 23 10:09:29 PST 2009


------- Comment #13 from jianli at chromium.org  2009-02-23 10:09 PDT -------
(In reply to comment #12)
> Why do we need to split WorkerMessagingProxy? The bug description says it's to
> do cross-thread messaging in WebKit, but this works already, doesn't it?

This is because we want to reuse what's implemented for cross-thread messaging
in WebKit towards other platform, like Chromium. Without splitting
WorkerMessagingProxy, we will have to duplicate a lot of existing logic as in
WorkerMessagingProxy when implementing WorkerContextProxy and WorkerObjectProxy
in Chromium. To share as much code as possible and improve the consistency, we
propose splitting WorkerMessagingProxy into two halves. 

For WebKit (cross-thread):
 Worker -> WorkerContextCrossThreadProxy -> WorkerContext
        <- WorkerObjectCrossThreadProxy  <-

For Chromium (cross-process):
 Worker -> WorkerContextCrossProcessProxy <...> WorkerObjectCrossProcessProxy
<- WorkerContext
                     |                                      |
                     v                                      v
        <- WorkerObjectCrossThreadProxy         WorkerContextCrossThreadProxy

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the webkit-unassigned mailing list