Changes between Version 4 and Version 5 of ThreadCommunication


Ignore:
Timestamp:
Apr 14, 2011 2:36:23 PM (10 years ago)
Author:
levin@chromium.org
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ThreadCommunication

    v4 v5  
    17172. An object wants to be able to allow another thread to be able to call its methods.[[BR]]
    1818
    19 3. A function wants to call a method on another thread and wait until it is done. Allowing callbacks resulting from that to run in the web worker thread.
    20 This does look suspiciously like a nested message loop with a filter which many people regard as evil. The only reason to allow this capability is for synchronous calls from javascript to call to the main thread to get some work done and act like a synchronous call but there may be callbacks (e.g. when doing a sync xhr call.) Theoretically, the javascript engine could roll up its state into a closure and we could avoid the nested message loop but that capability doesn't exist in the engines that we deal with and would be very expensive to add to them.[[BR]]
     193. A function wants to call a method on another thread and wait until it is done and allow callbacks resulting from that to run in the originating thread.[[BR]]
     20This looks like a nested message loop with a filter which is generally regarded as bad. The only reason to allow this capability is for synchronous calls from javascript to call to the main thread to get some work done and act like a synchronous call but there may be callbacks (e.g. when doing a sync xhr call.) Theoretically, the javascript engine could roll up its state into a closure and we could avoid the nested message loop but that capability doesn't exist in the engines that we deal with and would be very expensive to add to them.[[BR]]
    2121
    2222The framework should track the dependencies to check for possible deadlocks.[[BR]]
     
    5555
    5656TBD
     57
     58'''Case study: File API from Workers'''
     59
     60TBD: In progress