db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>

%T Communicating Mobile Processes
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>
%A  Frederick R. M. Barnes, Peter H. Welch
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>
%E Ian R. East, David Duce, Mark Green,  Jeremy M. R. Martin, Peter H. Welch
%B Communicating Process Architectures 2004
%X This paper presents a new model for mobile processes in
   occam\-pi. A process, embedded anywhere in a dynamically
   evolving network, may suspend itself mid\-execution, be
   safely disconnected from its local environment, moved (by
   communication along a channel), reconnected to a new
   environment and reactivated. Upon reactivation, the process
   resumes execution from the same state (i.e. data values and
   code positions) it held when it suspended. Its view of its
   environment is unchanged, since that is abstracted by its
   synchronisation (e.g. channels and barriers) interface and
   that remains constant. The environment behind that interface
   will (usually) be completely different. The mobile process
   itself may contain any number of levels of dynamic
   sub\-network. This model is simpler and, in some ways, more
   powerful than our earlier proposal, which required a process
   to terminate before it could be moved. Its formal semantics
   and implementation, however, throw up extra challenges. We
   present details and performance of an initial
   implementation.