Rethinking software connectors

Kell, Stephen

doi:10.1145/1294917.1294918

Cited by 10 publications

(5 citation statements)

References 34 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The run-time environment design leverages the canonical 'pipe-and-filters' software component model [12], where POSIX processes are the atomic components, and communication objects accessible through file descriptors are the connectors [13]. Like POSIX pipes, those connectors have distinguished transmit (Tx) and receive (Rx) ports that must be opened in modes O_WRONLY and O_RDONLY respectively.…”

Section: Key Design Principlesmentioning

confidence: 99%

A Distributed Run-Time Environment for the Kalray MPPA®-256 Integrated Manycore Processor

Dinechin

Massas

Lager

et al. 2013

Procedia Computer Science

View full text Add to dashboard Cite

The Kalray MPPA R -256 is a single-chip manycore processor that integrates 256 user cores and 32 system cores in 28nm CMOS technology. These cores are distributed across 16 compute clusters of 16+1 cores, and 4 quad-core I/O subsystems. Each compute cluster and I/O subsystem owns a private address space, while communication and synchronization between them is ensured by data and control Networks-on-Chip (NoC). This processor targets embedded applications whose programming models fall within the following classes: Kahn Process Networks (KPN), as motivated by media processing; single program multiple data (SPMD), traditionally used for numerical kernels; and time-triggered control systems.We describe a run-time environment that supports these classes of programming models and their composition. This environment combines classic POSIX single-process multi-threaded execution inside the compute clusters and I/O subsystems, with a set of specific Inter-Process Communication (IPC) primitives that exploit the NoC architecture. We combine these primitives in order to provide the run-time support for the different target programming models. Interestingly enough, all these NoC-specific IPC primitives can be mapped to a subset of the classic synchronous and asynchronous POSIX file descriptor operations. This design thus extends the canonical 'pipe-and-filters' software component model, where POSIX processes are the atomic components, and IPC instances are the connectors.

show abstract

Section: Key Design Principlesmentioning

confidence: 99%

A Distributed Run-Time Environment for the Kalray MPPA®-256 Integrated Manycore Processor

Dinechin

Massas

Lager

et al. 2013

Procedia Computer Science

View full text Add to dashboard Cite

show abstract

“…A lot of work has also been devoted to connectors and include a classification framework [48], studies on connectors [87,41], and formally grounded works on connectors. For example, [69] presents an approach for formally specifying connector wrappers as protocol transformations, modularizing them, and reasoning about their properties, with the aim to resolve component mismatches.…”

Section: Automatic Synthesis Of Mediatorsmentioning

confidence: 99%

Application-Layer Connector Synthesis

Inverardi

Spalazzese

Tivoli

2011

Formal Methods for Eternal Networked Software Systems

View full text Add to dashboard Cite

Abstract. The heterogeneity characterizing the systems populating the Ubiquitous Computing environment prevents their seamless interoperability. Heterogeneous protocols may be willing to cooperate in order to reach some common goal even though they meet dynamically and do not have a priori knowledge of each other. Despite numerous efforts have been done in the literature, the automated and run-time interoperability is still an open challenge for such environment. We consider interoperability as the ability for two Networked Systems (NSs) to communicate and correctly coordinate to achieve their goal(s). In this chapter we report the main outcomes of our past and recent research on automatically achieving protocol interoperability via connector synthesis. We consider application-layer connectors by referring to two conceptually distinct notions of connector: coordinator and mediator. The former is used when the NSs to be connected are already able to communicate but they need to be specifically coordinated in order to reach their goal(s). The latter goes a step forward representing a solution for both achieving correct coordination and enabling communication between highly heterogeneous NSs. In the past, most of the works in the literature described efforts to the automatic synthesis of coordinators while, in recent years the focus moved also to the automatic synthesis of mediators. Within the Connect project, by considering our past experience on automatic coordinator synthesis as a baseline, we propose a formal theory of mediators and a related method for automatically eliciting a way for the protocols to interoperate. The solution we propose is the automated synthesis of emerging mediating connectors (i.e., mediators for short).

show abstract

“…Kell [14,15] focuses on adaptation on a binary, operating system level (shared objects in Unix). He identifies two myths about component based software development: that there is a notion of a "matching module" that can be discovered and plugged in, and that development of components occurs in order: depended-on first, dependent later.…”

Section: Evolution and Adaptationmentioning

confidence: 99%

Poplar: A Java Extension for Evolvable Component Integration

Nyström-Persson,

Honiden

2011

Preprint

View full text Add to dashboard Cite

The Java programming language contains many features that aid component-based software development (CBSD), such as interfaces, visibility levels, and strong support for encapsulation. However, component evolution often causes so-called breaking changes, largely because of the rigidity of component interconnections in the form of explicit method calls and field accesses. We present a Java extension, Poplar, which we are currently developing. In Poplar, intercomponent dependencies are expressed using declarative queries; concrete linking code, generated using a planning algorithm, replaces these at compile time. Poplar includes a minimal specification language based on typestate-like protocols and labels, and a lightweight effect system, which ensures the absence of unwanted interference between handwritten code and generated code. We give several examples of fully automatic component integration using Poplar, and demonstrate its potential to simplify object-oriented software development greatly through evolvable and statically checkable integration links.

show abstract

Rethinking software connectors

Cited by 10 publications

References 34 publications

A Distributed Run-Time Environment for the Kalray MPPA®-256 Integrated Manycore Processor

A Distributed Run-Time Environment for the Kalray MPPA®-256 Integrated Manycore Processor

Application-Layer Connector Synthesis

Poplar: A Java Extension for Evolvable Component Integration

Contact Info

Product

Resources

About