Based on the initial refactoring of WorkerMessagingProxy class, I've updated
the abstractions as the following:
// A proxy to talk to the worker context.
// All calls to any methods should come from worker object thread.class
WorkerContextProxyBase {
public:
// Creator.
static WorkerContex
The current WebKit implementation of HTML5 workers is based on cross-thread
communication in single process. To make it work for Chrome, we need to run
the workers in Chrome's worker process. Hence, we propose the following
changes:
MessagingWorkerProxy acts as the gateway between Worker and Worke
2 matches
Mail list logo
