Efficient and language-independent mobile programs

Adl-Tabatabai, Ali-Reza; Langdale, Geoff; Lucco, Steven; Wahbe, Robert

doi:10.1145/231379.231402

Cited by 60 publications

(31 citation statements)

References 24 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…-The term mobile code describes any program that can be shipped unchanged to a heterogeneous collection of processors and executed with identical semantics on each processor [Adl-Tabatabai et al 1996]. -Mobile code is an approach where programs are considered as documents, and should therefore be accessible, transmitted, and displayed (i.e., evaluated) as any other document [Rouaix 1996].…”

Section: Why Mobile Code?mentioning

confidence: 99%

“…In the Omniware model [Adl-Tabatabai et al 1996] the overhead of interpretation is eliminated through software fault isolation (SFI). Code for the Omniware abstract machine is translated almost directly into native machine code, but all memory accesses are translated to code that checks for accesses outside a given boundary.…”

Section: The Abstract-machine Levelmentioning

confidence: 99%

“…Using a language-independent abstract machine retains all the language independence of the operating system solution, but does not have the portability problems. In the simplest version, the protection boundaries are enforced by an interpreter, performing all the needed checks at run-time.In the Omniware model [Adl-Tabatabai et al 1996] the overhead of interpretation is eliminated through software fault isolation (SFI). Code for the Omniware abstract machine is translated almost directly into native machine code, but all memory accesses are translated to code that checks for accesses outside a given boundary.…”

mentioning

confidence: 99%

See 2 more Smart Citations

Programming languages for mobile code

Thorn

1997

ACM Comput. Surv.

View full text Add to dashboard Cite

Sun's announcement of the programming language Java more than anything popularized the notion of mobile code, that is, programs traveling on a heterogeneous network and automatically executing upon arrival at the destination. We describe several classes of mobile code and extract their common characteristics, where security proves to be one of the major concerns. With these characteristics as reference points, we examine six representative languages proposed for mobile code. The conclusion of this study leads to our recommendations for future work, illustrated by examples of ongoing research. Additional Key Words and Phrases: Distribution, formal methods, Java, Limbo, mobile code, network programming, Objective Caml, Obliq, object orientation, portability, Safe-Tcl, safety, security, Telescript WHY MOBILE CODE?The expression "mobile code" has various different meanings in the literature. Just to take three examples, let us cite the following.-The term mobile code describes any program that can be shipped unchanged to a heterogeneous collection of processors and executed with identical semantics on each processor [Adl-Tabatabai et al. 1996]. -Mobile code is an approach where programs are considered as documents, and should therefore be accessible, transmitted, and displayed (i.e., evaluated) as any other document [Rouaix 1996]. -Mobile agents are code-containing objects that may be transmitted between communicating participants in a distributed system [Knabe 1996].In this survey we refer to mobile code as software that travels on a heterogeneous network, crossing protection domains, and automatically executed upon arrival at the destination. Protection domains can be as big as a corporate network and as small as a personal hand-held digital assistant. We believe that this characterization is general enough to encompass most usages and This work was performed under the auspices of Dyade (an R&D joint venture between Bull and Inria). Author's address: T. Thorn, Inria/Irisa, Campus de Beaulieu, 35042 Rennes Cedex, France; email: ͗thorn@irisa.fr͘. Permission to make digital / hard copy of part or all of this work for personal or classroom use is granted without fee provided that the copies are not made or distributed for profit or commercial advantage, the copyright notice, the title of the publication, and its date appear, and notice is given that copying is by permission of the ACM, Inc. To copy otherwise, to republish, to post on servers, or to redistribute to lists, requires prior specific permission and / or a fee. © 1997 ACM 0360-0300/97/0300-0213 $03.50 ACM Computing Surveys, Vol. 29, No. 3, September 1997 precise enough to exhibit the distinctive features of this technique. For example, it excludes the cases where code is loaded from a shared disk or downloaded (manually) from the Web.Mobile code supports a flexible form of distributed systems where the desired nonlocal computations need not be known in advance at the execution site. The advantages of this model are many, including: -Efficiency. When repe...

show abstract

Section: Why Mobile Code?mentioning

confidence: 99%

Section: The Abstract-machine Levelmentioning

confidence: 99%

mentioning

confidence: 99%

See 1 more Smart Citation

Programming languages for mobile code

Thorn

1997

ACM Comput. Surv.

View full text Add to dashboard Cite

show abstract

“…However, other processor architectures could be used just as easily, including purely emulation-based instruction sets such as Omniware [2] or Java bytecode [25]. The only restriction is that application processes must only use the subset of the instruction set that satisfies the properties described in Section 3; otherwise they may not function properly in virtualized environments.…”

Section: Basic Computational Instruction Setmentioning

confidence: 99%

Microkernels meet recursive virtual machines

Ford¹,

Hibler²,

Lepreau³

et al. 1996

Proceedings of the Second USENIX Symposium on Operating Systems Design and Implementation

View full text Add to dashboard Cite

This paper describes a novel approach to providing modular and extensible operating system functionality and encapsulated environments based on a synthesis of microkernel and virtual machine concepts. We have developed a software-based virtualizable architecture called Fluke that allows recursive virtual machines (virtual machines running on other virtual machines) to be implemented efficiently by a microkernel running on generic hardware. A complete virtual machine interface is provided at each level; efficiency derives from needing to implement only new functionality at each level. This infrastructure allows common OS functionality, such as process management, demand paging, fault tolerance, and debugging support, to be provided by cleanly modularized, independent, stackable virtual machine monitors, implemented as user processes. It can also provide uncommon or unique OS features, including the above features specialized for particular applications' needs, virtual machines transparently distributed cross-node, or security monitors that allow arbitrary untrusted binaries to be executed safely. Our prototype implementation of this model indicates that it is practical to modularize operating systems this way. Some types of virtual machine layers impose almost no overhead at all, while others impose some overhead (typically 0-35%), but only on certain classes of applications.

show abstract

“…A possible solution to overcome the problem of limited terminal mobility could be mobile code, which is defined by (Adl-Tabatabai et al, 1996) as "any program that can be shipped unchanged to a heterogeneous collection of processors and executed with identical semantics on each processor." In times when device connectivity is not available, mobile code might be shipped to the device and executed there in order to provide the service that would otherwise not be available in offline mode.…”

Section: Mobile Codementioning

confidence: 99%

Hybrid Application Support for Mobile Information Systems

Gruhn¹,

Hülder

2005

Proceedings of the Seventh International Conference on Enterprise Information Systems

View full text Add to dashboard Cite

Abstract:The wide-spread presence of wireless networks and the availability of mobile devices has enabled the development of mobile applications that take us a step closer to accomplishing Weiser's vision of ubiquitous computing (Weiser, 1991). Unfortunately however, network connectivity is still not given anywhere and at any time. To increase the benefit of mobile applications, the next logical step is to provide support for an offline modethat allows to continuously work with an application, even when the device is not connected to a network. In this paper typical problems of replicating data are explained, possible solutions are discussed and two architectural patterns that could be used to implement hybrid support are illustrated.

show abstract

Efficient and language-independent mobile programs

Cited by 60 publications

References 24 publications

Programming languages for mobile code

Programming languages for mobile code

Microkernels meet recursive virtual machines

Hybrid Application Support for Mobile Information Systems

Contact Info

Product

Resources

About