Back

nextupprevious
Next:Example of ExecutionUp:The Distributed Implementation ofPrevious:Behavior of ambients

Migration of ambients on network environments

Ambient can express not only processes, but also computers in which the processes are running and among which processes migrate. Thus, the root ambients must represent the computers, whose domain names are used as the names of the ambients. We call such ambients machine ambients. In our laboratory, we have computers koon and est.

$\displaystyle koon[n[out koon]]$
\includegraphics[keepaspectratio,clip]{4.eps}
Fig 2: How can ambients exit from machine ambient
Though processes can exit machine ambients, they can not become machine ambients. In such a case, capability in to other machine ambient must be executed immediately.

$\displaystyle koon[n[out koon.in est]]$
\includegraphics[keepaspectratio,clip]{5.eps}
Fig 3: Migration of Ambient Objects among computers
Before Ambient object migrates, it must be serialized. Then it is transmitted to the destination.
\includegraphics[keepaspectratio,clip]{6.eps}
Fig: HORB Proxy
When an ambient tries to exit a computer, the machine ambient creates the HORB Proxy which represents the destination computer. Instead of transmitting the migrating ambient to the destination computer, we only have to transmit the ambient to the Proxy. Then the HORB mechanism automatically send the object to the destination.


nextupprevious
Next:Example of ExecutionUp:The Distributed Implementation ofPrevious:Behavior of ambients

 Back