mobile

Interpreter Using an abstract interpreter has been a very popular way of implementing safe and portable computation. Mobile code languages like Java [53], Safe Tcl [84], Scheme48 [91], and Telescript [124], all involve the interpretation of some source or intermediate languages. The interpreter approach can achieve memory protection in two ways: 1. A safe intermediate representation can be defined for mobile code units. Due to language restrictions, certain unsafe operations cannot be expressed, while others can be statically checked for. Take the JVM bytecode representation [67] as example. Privileged native instructions cannot be expressed; there is no pointer arithmetic; the language is strictly typed; interactions with the host's resources are performed through public application programming interface (API) [19]. As a result, memory interference can be avoided. 2. The execution unit interacts with the host's CPU only through the arbitration of the interpreter. Consequently, the in...