Reliable distributed computing with Avalon/Common Lisp

Clamen, Stewart M.; Leibengood, L.D.; Nettles, Scott; Wing, Jeannette M.

doi:10.1109/iccl.1990.63772

Cited by 9 publications

(5 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In the late 1980s, researchers interested in distributed programming languages began to explore the idea of generalizing RPC along the directions seen in NeWS [13]- [16]. The resulting remote evaluation systems had a simple model of computation, code could be shipped to a remote node and then evaluated.…”

Section: B Remote Evaluationmentioning

confidence: 99%

“…RPC is a special case where the code that is shipped is just a function call and its arguments. Both Stamos [13]- [15] and Clamen [16] used Lisp dialects as the basis for their remote evaluation systems because Lisp made representing programs (and most data) in a format that could be sent from machine to machine (ASCII byte streams) simple. Such representations also had the advantage of support for heterogeneous machine types [17], a problem for most process migration schemes.…”

Section: B Remote Evaluationmentioning

confidence: 99%

See 1 more Smart Citation

Active Networking: One View of the Past, Present, and Future

Smith

Nettles

2004

IEEE Trans. Syst., Man, Cybern. C

Self Cite

View full text Add to dashboard Cite

All distributed computing systems face the architectural question of the location (and nature) of programmability in the telecommunications networks, computers, and other peripheral devices comprising them. The perspective of this paper is that network elements should be as programmable as possible, to enable the most flexible distributed computing systems.There has been a persistent confluence among operating systems, programming languages, networking and distributed systems. We demonstrate how these interactions led to what is called "active networking", and in the spirit of "vox audita perit, littera scripta manet" (the spoken word perishes, but the written word remains), include an account of how it was made to happen. Lessons are drawn both from the broader research agenda, and the specific goals pursued in the SwitchWare project. We speculate on likely futures for active networking. This material is posted here with permission of the IEEE. Such permission of the IEEE does not in any way imply IEEE endorsement of any of the University of Pennsylvania's products or services. Internal or personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution must be obtained from the IEEE by writing to pubs-permissions@ieee.org. By choosing to view this document, you agree to all provisions of the copyright laws protecting it.This journal article is available at ScholarlyCommons: http://repository.upenn.edu/cis_papers/46 4 IEEE TRANSACTIONS ON SYSTEMS, MAN, AND CYBERNETICS-PART C: APPLICATIONS AND REVIEWS, VOL. 34, NO. 1, FEBRUARY 2004 Active Networking: One View of the Past, Present, and Future Jonathan M. Smith, Fellow, IEEE, and Scott M. Nettles, Member, IEEE Abstract-All distributed computing systems face the architectural question of the location (and nature) of programmability in the telecommunications networks, computers, and other peripheral devices comprising them. The perspective of this paper is that network elements should be as programmable as possible, to enable the most flexible distributed computing systems.There has been a persistent confluence among operating systems, programming languages, networking and distributed systems. We demonstrate how these interactions led to what is called "active networking," and in the spirit of "vox audita perit, littera scripta manet" (the spoken word perishes, but the written word remains), include an account of how it was made to happen. Lessons are drawn both from the broader research agenda, and the specific goals pursued in the SwitchWare project. We speculate on likely futures for active networking.

show abstract

Section: B Remote Evaluationmentioning

confidence: 99%

Section: B Remote Evaluationmentioning

confidence: 99%

Active Networking: One View of the Past, Present, and Future

Smith

Nettles

2004

IEEE Trans. Syst., Man, Cybern. C

Self Cite

View full text Add to dashboard Cite

show abstract

“…Most mobile code languages have selected one of these two alternatives. Agent Tcl [8], Telescript [13] and Aglets [11] use a go-based mechanism, whereas Obliq [7], Avalon [4], NCL [5], REV [6] and TACOMA [12] use a function-call-based interface. To ensure a prompt response to asynchronous events, a function-call-based interface would require one of two things: (i) either the language automatically captures the continuation at the point at which an event occurs and makes it available for use within the corresponding event handler; or (ii) the programmer emulates this functionality by writing a large number of functions that represent continuations at different points in the programs.…”

Section: Agilitymentioning

confidence: 99%

“…The simplest form of support is the ability to download code and execute it to completion at a single site -as provided by systems like Omniware [1], Safe-TCL [2] and Java [3]. Other systems like Avalon [4], NCL [5], REV [6] and Obliq [7] allow programs in execution to initiate computation on remote nodes and wait for their completion. The most sophisticated support is provided by systems like Agent Tcl [8], Emerald [9], Mole [10], Aglets [11], TACOMA [12] and Telescript [13] which permit an executing program to move while it is in execution.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Resource‐aware metacomputing

Acharya

Ranganathan

Saltz

1997

Concurrency: Pract. Exper.

View full text Add to dashboard Cite

SUMMARYIn this paper we outline some potential applications of resource-aware scheduling to highperformance metacomputing applications and describe requirements associated with the use of mobility for resource-aware scheduling. Programs that use mobility as a mechanism to adapt to resource changes have three requirements that are not shared with other mobile programs. Firstly, they need to monitor the level and quality of resources in their operating environment. Secondly, they need to be able to react to changes in resource availability. Thirdly, they need to be able to control the way in which resources are used on their behalf (by libraries and other support code). In this paper, we describe the design and implementation of Sumatra, an extension of Java that supports resource-aware mobile programs. We also describe the design and implementation of a distributed resource monitor that provides the information required by Sumatra programs. Finally, we present a prototype resource-aware data intensive program that combines and composes weather images from multiple geographically distributed sources.

show abstract