A type language for message passing component-based systems

Abstract

Component-based development is challenging in a distributed setting, for starters considering programming a task may involve the assembly of loosely-coupled remote components. In order for the task to be fulfilled, the supporting interaction among components should follow a well-defined protocol. In this paper we address a model for message passing component-based systems where components are assembled together with the protocol itself. Components can therefore be independent from the protocol, and reactive to messages in a flexible way. Our contribution is at the level of the type language that allows to capture component behaviour so as to check its compatibility with a protocol. We show the correspondence of component and type behaviours, which entails a progress property for components.

A Service Discovery Solution for Edge Choreography-Based Distributed Embedded Systems

“…In recent years, service composition modeling under choreography paradigm has been addressed in several platforms such as CHOReOS [19,20] and its evolution into CHOReV-OLUTION [21]; ActnConnect [22]; ChorSystem [23]; and research works such as [24][25][26][27][28]. Extensions integrated within choreography add functionality oriented to different scenarios [29][30][31][32].…”

Composition and decomposition of multiparty sessions

“…As far as we know, modularity of choreographic models has not been explored much. An exception is the approach recently proposed in [14,42]. Modularity is attained by means of a specified protocol regulating the communications at the "interface".…”

“…Roughly speaking, this protocol represents the composition interface that rules out, among the communications of components, those not allowed in the composition. Components in [14,42] are reactive (similarly to [24,25]). More precisely, components exports their input and output ports which are connected by links.…”

Composing Communicating Systems, Synchronously

“…A compositional approach for reactive components has been proposed in [12,25]. Composition is attained by means of a specified protocol regulating the communications between components that are supposed to produce results as soon as they get their inputs.…”

“…In this way, a component may be used in compositions under different protocols if its communications are compliant with (part of) the protocols. A difference with our approach is that the framework in [12,25], as common in session type approaches, requires the specification of a global type from which to derive local types to type check components in order to compose them.…”