summaryrefslogtreecommitdiffstats
path: root/chrome/worker
Commit message (Collapse)AuthorAgeFilesLines
* Fill out some of the new abstract methods of WebKitClient.ericroman@google.com2009-03-082-0/+20
| | | | | | | | | | | | | | | | This is a quickie to get things compiling -- after I updated DEPS to land webkit merge, I picked up your r11178 which changed these interfaces. Note, it looks like there is a reachability problem with ChromiumBridge::initV8CounterFunction() -- I had to remove the implementation from chromium_bridge_impl.cc to avoid multiple definitions (already in ChromiumBridge.cpp)... however that version does: ASSERT_NOT_REACHED(); This is a problem, since v8_proxy.cpp still calls it... this might crash in debug mode, but hopefully makes tree a bit happier... TBR=darin Review URL: http://codereview.chromium.org/40277 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@11211 0039d316-1c4b-4281-b951-d872f2087c98
* Reland r11118.darin@chromium.org2009-03-062-0/+11
| | | | | | | | TBR=dglazkov Review URL: http://codereview.chromium.org/40240 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@11137 0039d316-1c4b-4281-b951-d872f2087c98
* Revert r11118 :(darin@chromium.org2009-03-062-11/+0
| | | | | | | | TBR=dglazkov Review URL: http://codereview.chromium.org/39267 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@11125 0039d316-1c4b-4281-b951-d872f2087c98
* WorkerWebKitClientImpl snuck up on me. arggh!darin@chromium.org2009-03-062-0/+11
| | | | | | | | | | | This implementation is similar to the one we have TestShell, which is to say that we don't support visited links in the Worker process. TBR=dglazkov Review URL: http://codereview.chromium.org/40230 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@11121 0039d316-1c4b-4281-b951-d872f2087c98
* Hook up WebKit worker with Chromium.jianli@chromium.org2009-03-058-25/+92
| | | | | | Review URL: http://codereview.chromium.org/39147 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@11046 0039d316-1c4b-4281-b951-d872f2087c98
* Fixes CRLF and trailing white spaces.maruel@chromium.org2009-03-051-1/+1
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@10982 0039d316-1c4b-4281-b951-d872f2087c98
* Add DEPS file for chrome/workerjam@chromium.org2009-03-041-0/+6
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@10849 0039d316-1c4b-4281-b951-d872f2087c98
* Initial checkin of the out of process worker implementation.jam@chromium.org2009-03-049-0/+574
WebWorkerClient/WebWorker are parallel interfaces of WebCore::{WorkerObjectProxy, WorkerContextProxy} that use Chrome data types. When WebKit requests a WorkerObjectProxy, we create an instance of WebWorkerClientImpl. This class creates an object that implements a Chromium version of WorkerObjectProxy (i.e. with Chrome data types) through WebViewDelegate. That object is a WebWorkerProxy and talks over IPC to a WebWorker object in the worker process. The WebWorker object creates the actual WebCore::Worker object using another class in glue: WebWorkerImpl. When the WebCore::Worker object running in the worker process wants to talk back to the code running in the renderer, it talks to WebWorkerImpl which implements WebCore::WorkerObjectProxy. WebWorkerImpl converts the data types to Chrome compatible ones, and then calls the WebWorkerClient version which does IPC to get to the renderer process. This ends up at WebWorkerProxy, which calls WebWorkerClientImpl (the original class). In future changes, sandboxing, multiple worker processes etc will be added. Note that I also had to make two small changes to WebKit, since WorkerMessagingProxy couldn't be created as is for the nested worker case. I'll either check it in myself or work with Jian to do so. Review URL: http://codereview.chromium.org/27157 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@10847 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-01-20 13:01:55 +0000