Changes between Version 7 and Version 8 of ThreadCommunication

Timestamp:

Apr 20, 2011, 2:03:33 PM (14 years ago)

Author:

levin@chromium.org

Comment:

Filled in api for sync case.

ThreadCommunication

@@ -48 +48 @@
 {{{
     // getProxy is a method in the current object which returns its proxy. The proxy may be used with invoke like these examples.
-    proxy->invoke(&TypeName::method, arg1, getProxy(), arg3, ...);
+    proxy->invokeWithCallback(this, &TypeName::method, arg1, arg2, arg3, ...);
 }}}
+
+The resulting call on TypeName::method should look identical to that done with invokeSync.  (The other side doesn't care and should indicate when it is "done" so it may be used in either way.)
 
 
 Case 3: A thread wants to call a function on another thread and wait until it is done.
 
-TBD
+{{{
+    OwnPtr<SyncWaiter> syncCall = proxy->invokeSync(this, &TypeName::method,  arg1, arg2, arg3, ...);
+    syncCall.wait();
+}}}
+
 
 '''Case study: File API from Workers'''
@@ -102 +108 @@
 void WorkerFileSystemCallbacks::postMoveToMainThread(WebFileSystem* fileSystem, const String& sourcePath, const String& destinationPath, const String& mode)
 {
-    OwnPtr<SyncWaiter> syncCall = mainThreadMessageLoop->invokeSync(&moveOnMainThread, fileSystem, sourcePath, destinationPath);
+    OwnPtr<SyncWaiter> syncCall = mainThreadMessageLoop->invokeSync(this, &moveOnMainThread, fileSystem, sourcePath, destinationPath);
     syncCall.wait();
     stop();
 }
 }}}
+
+This introduced a way to to call a function on the other thread (Messageloop::invokeSync).
+
+
+'''Detailed api breakdown'''
+
+TBD