Changes between Version 2 and Version 3 of JavaParty/DistributedThreads


Ignore:
Timestamp:
Feb 12, 2005 4:37:18 PM (15 years ago)
Author:
hauma
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • JavaParty/DistributedThreads

    v2 v3  
    11= Distributed Threads =
     2[[JPNav]]
    23
    34When a remote method is called, the actual thread sends the method arguments and blocks until the method result is available. After reception of the result, it continues. On the server side, a thread unrelated to the original one receives the method invocation, executes the requested method and returns the result over the network. From a bird's eye view, the control flow moves during the remote call from one virtual machine to another and returns to the original machine when the method returns. Such control flow that spawns multiple nodes is called a "distributed thread". Since Java threads are bound to their virtual machine they are created in, a remote method execution is mapped to two different Java threads: the client thread that initiated the call, and the server thread that executes the remote method on the remote node. These two threads are both representatives for the same distributed thread of control. Each segment of the distributed thread is mapped to a particular local Java thread for execution.