Journal Article10.1145/174625.174629
The POLYLITH software bus
TL;DR: A system called POLYLITH that helps programmers prepare and interconnect mixed-language software components for execution in heterogeneous environments so that once an application has been developed for use in one execution environment it can be adapted for reuse in other environments by automatic techniques.
read more
Abstract: We describe a system called POLYLITH that helps programmers prepare and interconnect mixed-language software components for execution in heterogeneous environments. POLYLITH's principal benefit is that programmers are free to implement functional requirements separately from their treatment of interfacing requirements; this means that once an application has been developed for use in one execution environment (such as a distributed network) it can be adapted for reuse in other environments (such as a shared-memory multiprocessor) by automatic techniques. This flexibility is provided without loss of performance. We accomplish this by creating a new run-time organization for software. An abstract decoupling agent, called the software bus, is introduced between the system components. Heterogeneity in language and architecture is accommodated since program units are prepared to interface directly to the bus and not to other program units. Programmers specify application structure in terms of a module interconnection language (MIL); POLYLITH uses this specification to guide packaging (static interfacing activities such as stub generation, source program adaptation, compilation, and linking). At run time, an implementation of the bus abstraction may assist in message delivery, name service, or system reconfiguration.
read more
Chat with Paper
AI Agents for this Paper
Find similar papers on Google Scholar, PubMed and Arxiv
Write a critical review of this paper
Analyze citations of this paper to find unaddressed research gaps
Citations
A formal basis for architectural connection
Robert J. Allen,David Garlan +1 more
TL;DR: The key idea is to define architectural connectors as explicit semantic entities as a collection of protocols that characterize each of the participant roles in an interaction and how these roles interact.
Architecture-based runtime software evolution
Peyman Oreizy,Nenad Medvidovic,Richard N. Taylor +2 more
- 01 Apr 1998
TL;DR: An architecture-based approach to runtime software evolution is presented and the role of software connectors in supporting runtime change is highlighted and an initial implementation of a tool suite for supporting the runtime modification of software architectures is presented.
Dynamic structure in software architectures
Jeff Magee,Jeff Kramer +1 more
- 01 Oct 1996
TL;DR: ADL features which permit the description of dynamic software architectures in which the organisation of components and connectors may change during system execution are examined.
Proceedings of the 1997 winter simulation conference
Kevin J. Healy
- 01 Jan 1997
Abstract: This tutorial discusses the issues and procedures for using simulation as a tool for optimization of stochastic complex systems that are modeled by computer simulation. It is intended to be a tutorial rather than an exhaustive literature search. Its emphasis is mostly on issues that are specific to simulation optimization instead of concentrating on the general optimization and mathematical programming techniques, Even though a lot of effort has been spent to provide a comprehensive overview of the field, still there are methods and techniques that have not been covered and valuable works that may not have been mentioned.
Formalizing architectural connection
Robert J. Allen,David Garlan +1 more
- 21 May 1994
TL;DR: A theory is presented for one aspect of architectural description, the interactions between components, to define architectural connectors as explicit semantic entities that characterize each of the participant roles in an interaction and how these roles interact.
422
References
Programming-in-the large versus programming-in-the-small
Frank DeRemer,Hans Kron +1 more
- 01 Jan 1975
TL;DR: The activity of writing large programs is distinguished from that of writing small ones, which means systems consisting of many small programs (modules), usually written by different people.
587
The V distributed system
TL;DR: The V distributed System was developed at Stanford University as part of a research project to explore issues in distributed systems.
524
Promises: linguistic support for efficient asynchronous procedure calls in distributed systems
Barbara Liskov,Liuba Shrira +1 more
- 01 Jun 1988
TL;DR: A new data type called a promise is described that was designed to support asynchronous calls that allow a caller to run in parallel with a call and to pick up the results of the call, including any exceptions it raises, in a convenient and type-safe manner.
398
XDR: External Data Representation Standard
R. Srinivasan
- 01 Aug 1995
TL;DR: This document describes the External Data Representation Standard (XDR) protocol as it is currently deployed and accepted.