Linda in context

Carriero, Nicholas; Gelernter, David

doi:10.1145/63334.63337

Cited by 1,121 publications

(411 citation statements)

References 26 publications

Supporting

Mentioning

407

Contrasting

Unclassified

Order By: Relevance

“…However, this is only for the sake of simplicity of our presen-tation. In fact, our regulatory mechanism applies to a P/S mediator consisting of multiple, distributed processes, working in concert, just as well 4 . Particularly, no change in law AP below would be required to regulate the use of such a P/S mediator of a distributed architecture.…”

Section: Implementation Of the Alarm Policymentioning

confidence: 99%

“…Among several techniques that have been developed to support such communication -which effectively decouples the producers of information from its consumers, both in time and in space [5] -the most prominent are: the publish/subscribe (P/S, for short) [6,14], and the Linda-like tuple-space [4,12] middlewares. The publish/subscribe paradigm, which we will take here as a representative of what enables decoupled communication, provides mediators between the producers of information (which we call here informers), and its consumers (the clients, or subscribers).…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

On Shouting “Fire!”: Regulating Decoupled Communication in Distributed Systems

Minsky¹

2003

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Decoupled communication, which requires no direct association between the producers of information and its consumers -as under the publish/subscribe (P/S) middleware -is often essential for the integration of distributed and heterogeneous applications. But the indefinite, and potentially global, reach of decoupled communication -the very reason for its power -has a dark side, which may complicate the system using it, making it less predictable, more brittle, and less safe. Just think about the effect of shouting "fire" in a packed theatre, particularly, but not only, if it is a false alarm. It is our thesis that the inherent drawbacks of decoupled communication can be tamed by decentralized regulation of its use. We show how such regulation can be carried out scalably by means of a distributed control mechanism called Law-Governed Interaction (LGI), and a middleware called Moses that implements this mechanism. Along the way, we illustrate the importance of such regulation, and its effectiveness, by considering the treatment of alarms in a large hospital.

show abstract

Section: Implementation Of the Alarm Policymentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

On Shouting “Fire!”: Regulating Decoupled Communication in Distributed Systems

Minsky¹

2003

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…Coordination problems, however, cannot always be solved by solely using a particular model. Furthermore, data-driven coordination approaches such as Linda [9] do not enforce a clear separation of concerns as a mixture of coordination and computation code within an agent is still possible. Finally, coordination languages generally do not allow the definition of reusable coordination abstractions at a higher level than the basic mechanisms and paradigms supported by the underlying model.…”

Section: A Conceptual Framework For Software Compositionmentioning

confidence: 99%

Agent Coordination via Scripting Languages

Schneider

Lumpe

Nierstrasz

2001

Coordination of Internet Agents

View full text Add to dashboard Cite

Summary.In recent years, so-called scripting languages have become increasingly popular as they provide means to build quickly flexible applications from a set of prefabricated components. These languages typically support a single, specific architectural style of composing components (e.g. the pipes and filters architectural style), and they are designed to address a specific application domain. Although scripting languages and coordination languages have evolved from different roots and have been developed to solve different problems, we argue that both address similar separations of concerns. Scripting languages achieve a separation of components from the scripts that configure and compose them, whilst coordination languages separate computational entities from the coordination code that manages dependencies between them. In this chapter we will define coordination in the context of a conceptual framework for component-based software development. Furthermore, we will discuss main properties and abstractions of scripting languages and will compare selected scripting languages with respect to the identified core concepts. Finally, using a small set of sample applications, we will illustrate the power and the limitations of these concepts in order to define agent coordination.

show abstract

“…The join-calculus [20] approaches this problem by rooting each channel at a particular process; this provides a single place where synchronization is resolved. LLinda [18] is a formalization of Linda [15] using process calculi techniques; as in distributed versions of Linda, LLinda has multiple distributed tuple spaces, each with its local synchronization manager.…”

Section: Distributionmentioning

confidence: 99%

“…• Linda [15]. Linda is a "coordination language" where multiple processes interact in a common space (called a tuple space) by dropping and picking up tokens asynchronously.…”

Section: Related Languagesmentioning

confidence: 99%