| Join-pattern | |
| Paradigm: | concurrent computing, distributed programming |
| Implementations: | Join Java, Polyphonic C#, Unified Parallel C, Cω, Joins library, Boost. |
| Influenced: | Join Calculus |
| Developer: | INRIA Inria |
| Website: | Inria Join |
Join-patterns provides a way to write concurrent, parallel and distributed computer programs by message passing. Compared to the use of threads and locks, this is a high level programming model using communication constructs model to abstract the complexity of concurrent environment and to allow scalability. Its focus is on the execution of a chord between messages atomically consumed from a group of channels.
This template is based on join-calculus and uses pattern matching. Concretely, this is done by allowing the join definition of several functions and/or channels by matching concurrent call and messages patterns. It is a type of concurrency pattern because it makes easier and more flexible for these entities to communicate and deal with the multi-threaded programming paradigm.
The join-pattern (or a chord in Cω) is like a super pipeline with synchronisation and matching. In fact, this concept is summarise by match and join a set of message available from different message queues, then handles them all simultaneously with one handler.[1] It could be represented by the keywords to specify the first communication that we expected, with the to join/pair other channels and the to run some tasks with the different collected messages. A constructed join pattern typically takes this form:
More precisely, when a message matches with a chain of linked patterns causes its handler to run (in a new thread if it's in asynchronous context) otherwise the message is queued until one of its patterns is enabled; if there are several matches, an unspecified pattern is selected.[2]
Join-pattern is defined by a set of pi-calculus channels that supports two different operations, sending and receiving, we need two join calculus names to implement it: a channel name for sending (a message), and a function name for receiving a value (a request). The meaning of the join definition is that a call to returns a value that was sent on a channel . Each time functions are concurrently, triggers the return process and synchronizes with other joins.[3]
In most of cases, the order of synchronous calls is not guaranteed for performance reasons. Finally, during the match the messages available in the queue could be stolen by some intervening thread; indeed, the awakened thread may have to wait again.[4]
The π-calculus belongs to the family of process calculi, allows mathematical formalisms for describing and analyzing properties of concurrent computation by using channel names to be communicated along the channels themselves, and in this way it is able to describe concurrent computations whose network configuration may change during the computation.
Join patterns first appeared in Fournet and Gonthier’s foundational join-calculus, an asynchronous process algebra designed for efficient implementation in a distributed setting.[5] The join-calculus is a process calculus as expressive as the full π-calculus. It was developed to provide a formal basis for the design of distributed programming languages, and therefore intentionally avoids communications constructs found in other process calculi, such as rendezvous communications.
The Join-Calculus is both a name passing calculus and a core language for concurrent and distributed programming.[6] That's why the Distributed Join-Calculus[7] based on the Join-Calculus with the distributed programming was created on 1996. This work use the mobile agents where agents are not only programs but core images of running processes with their communication capabilities.
JoCaml[8] [9] and Funnel[10] [11] are functional languages supporting declarative join patterns. They present the ideas to direct implement a process calculi in a functional setting.
Another extensions to (non-generic) Java, JoinJava, were independently proposed by von Itzstein and Kearney.[12]
Cardelli, Benton and Fournet proposed an object-oriented version of join patterns for C# called Polyphonic C#.[13]
Cω is adaptation of join-calculus to an object-oriented setting.[14] This variant of Polyphonic C# was included in the public release of Cω (a.k.a. Comega) in 2004.
Scala Joins is a library to use Join-Pattern with Scala in the context of extensible pattern matching in order to integrate joins into an existing actor-based concurrency framework.[15]
Erlang is a language which natively supports the concurrent, real time and distributed paradigm. Concurrency between processes was complex, that's why the project build a new language, JErlang (J stands for Join) using based on the Join-calculus.
"Join-patterns can be used to easily encode related concurrency idioms like actors and active objects."[16]
for (int i = 0; i < n; i++)
A mobile agent is an autonomous software agent with a certain social ability and most importantly, mobility. It is composed of computer software and data which can move between different computers automatically while continuing their executions.
The mobile agents can be used to match concurrency and distribution if one uses the Join-calculus. That's why a new concept named "distributed Join-calculus" was created; it's an extension of Join-calculus with locations and primitives to describe the mobility.This innovation use agents as running processes with their communication capabilities to allow an idea of location, which is a physical site expressing the actual position of the agent. Thanks to the Join-calculus, one location can be moved atomically to another site.[21]
The processes of an agent is specified as a set which define its functionality including asynchronous emission of a message, migration to other location. Consequently, locations are organized in a tree to represent the movement of the agent easier. With this representation, a benefit of this solution is the possibility to create a simple model of failure. Usually a crash of a physical site causes the permanent failure of all its locations. But with the join-calculus a problem with a location can be detected at any other running location, allowing error recovery.
In 2007, an extension of the basic join calculus with methods which make agents proactive has come out. The agents can observe an environment shared between them. With this environment, it is possible to define shared variables with all agents (e.g. a naming service to discover agents between themselves).[22]
Join-languages are built on top of the join-calculus taken as a core language. So all the calculus are analysed with asynchronous processes and the join pattern provides a model to synchronize the result.
To do this, it exists two Compilers:
This two compiler works with the same system, an automaton.
It represents the consumption of message arrive at a completed join model. Each state is a possibly step for the code execution and each transitions is the reception of a message to change between two steps. And so when all messages are grab, the compiler execute the body join code corresponding to the completed model joint.
So in the join-calculus, the basic values are the names like on the example is A,B or C. So the two compiler representing this values with two ways.
Join compiler use a vector with Two slots, the first to the name it-self and the second to a queue of pending messages.
Jocaml use name like a pointer on definitions. This definitions store the others pointer of the others names with a status field and a matching date structure by message.
The fundamental difference is when the guard process is executed, for the first, it was verify if all names are the pending messages ready whereas the second use only one variable and access at the others to know if the model is completed.
Recent research describe the compilation scheme as the combination of two basic steps: dispatching and forwarding. The design and correctness of the dispatcher essentially stems from pattern matching theory, while inserting an internal forwarding step in communications is a natural idea, which intuitively does not change process behavior. They made the observation that the worth observing is a direct implementation of extended join-pattern matching at the runtime level would significantly complicate the management of message queues, which would then need to be scanned in search of matching messages before consuming them.[23]
There are many uses of the Join-patterns with different languages. Some languages use join-patterns as a base of theirs implementations, for example the Polyphonic C# or MC# but others languages integrate join-pattern by a library like Scala Joins[24] for Scala or the Joins library for VB.[25] Moreover, the join-pattern is used through some languages like Scheme to upgrade the join-pattern.[26]
| JErlang | CB | Joins Library | Polyphonic C# | Parallel C# | Cω | Scala Joins | F# | Scheme | Join Java | Hume | JoCaml | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Patterns matching | |||||||||||||
| Scheduler between join-patterns | : first match | : first/round robin | : random | : first/round robin | : random | ||||||||
| Generics | |||||||||||||
| Overriding |
Join Java[27] is a language based on the Java programming language allowing the use of the join calculus. It introduces three new language constructs:
Example:
Example:
Join fragments can be repeated in multiple Join patterns so there can be a case when multiple Join patterns are completed when a fragment is called. Such a case could occur in the example below if B, C and D then A are called. The final A fragment completes three of the patterns so there are three possible methods that may be called. The ordered class modifier is used here to determine which Join method will be called. The default and when using the unordered class modifier is to pick one of the methods at random. With the ordered modifier the methods are prioritised according to the order they are declared.
Example:
In Erlang coding synchronisation between multiple processes is not straightforward. That's why theJErlang,[28] an extension of Erlang was created, The J is for Join. Indeed, To overcome this limitation JErlang was implemented, a Join-Calculus inspired extension to Erlang.The features of this language are:
Yigong Liu has written some classes for the join pattern including all useful tools like asynchronous and synchronous channels, chords, etc. It's integrated in the project Boost c++.
This example shows us a thread safe buffer and message queue with the basic operations put and get.[29]
Polyphonic C# is an extension of the C# programming language. It introduces a new concurrency model with synchronous and asynchronous (which return control to the caller) methods and chords (also known as ‘synchronization patterns’ or ‘join patterns’).
MC# language is an adaptation of the Polyphonic C# language for the case of concurrent distributed computations.
Parallel C# is based Polyphonic C# and they add some new concepts like movables methods, high-order functions.
class Test13
This example demonstrates how to use joins.[31]
Cω adds new language features to support concurrent programming (based on the earlier Polyphonic C#). The Joins Concurrency Library for C# and other .NET languages is derived of this project.[32] [33]
It's an easy to use declarative and scalable join-pattern library. In opposite to the Russo library, it has no global lock. In fact, it's working with a compare-and-swap CAS and Atomic message system. The library[34] use three improvements for the join-pattern :
JoCaml is the first language where the join-pattern was implemented. Indeed, at the beginning all the different implementation was compiled with the JoCaml Compiler.JoCaml language is an extension of the OCaml language. It extends OCaml with support for concurrency and synchronization, the distributed execution of programs, and the dynamic relocation of active program fragments during execution.[35]
(* def defines a Join-pattern set clause * "&" in the left side of = means join (channel synchronism) * "&" in the right hand side means: parallel process * synchronous_reply :
def put(s) = print_endline s ; 0 (* STOP *) ;; (* put: string Join.chan *)
def serve(drink) = match drink with Coffee -> put("Cofee") | Tea -> put("Tea") ;; (* serve: drinks Join.chan *)
def refund(v) = let s = Printf.sprintf "Refund %d" v in put(s) ;; (* refund: int Join.chan *)
let new_vending serve refund = let vend (cost:int) (credit:int) = if credit >= cost then (true, credit - cost) else (false, credit) in def coin(Nickel) & value(v) = value(v+5) & reply to coin or coin(Dime) & value(v) = value(v+10) & reply to coin
or button(BCoffee) & value(v) = let should_serve, remainder = vend 10 v in (if should_serve then serve(Coffee) else 0 (* STOP *)) & value(remainder) & reply to button
or button(BTea) & value(v) = let should_serve, remainder = vend 5 v in (if should_serve then serve(Tea) else 0 (* STOP *)) & value(remainder) & reply to button
or button(BCancel) & value(v) = refund(v) & value(0) & reply to button in spawn value(0) ; coin, button (* coin, button: int -> unit *) ;; (* new_vending: drink Join.chan -> int Join.chan -> (int->unit)*(int->unit) *)
let ccoin, cbutton = new_vending serve refund in ccoin(Nickel); ccoin(Nickel); ccoin(Dime); Unix.sleep(1); cbutton(BCoffee); Unix.sleep(1); cbutton(BTea); Unix.sleep(1); cbutton(BCancel); Unix.sleep(1) (* let the last message show up *) ;;gives
Coffee Tea Refund 5
Hume[36] is a strict, strongly typed functional language for limited resources platforms, with concurrency based on asynchronous message passing, dataflow programming, and a Haskell like syntax.
Hume does not provide synchronous messaging.
It wraps a join-pattern set with a channel in common as a box, listing all channels in an in tuple and specifying all possible outputs in an out tuple.
Every join-pattern in the set must conform to the box input tuple type specifying a '*' for non required channels, giving an expression whose type conform to the output tuple, marking '*' the non fed outputs.
A wire clause specifies
A box can specify exception handlers with expressions conforming to the output tuple.
type Int = int 32 ;type String = string ;show u = u as string ;
box coffeein (coin :: Coins, button :: Buttons, value :: Int) -- input channelsout (drink_outp :: String, value’ :: Int, refund_outp :: String) -- named outputs
match-- * wildcards for unfilled outputs, and unconsumed inputs (Nickel, *, v) -> (*, v + 5, *)| (Dime, *, v) -> (*, v + 10, *)| (*, BCoffee, v) -> vend Coffee 10 v| (*, BTea, v) -> vend Tea 5 v| (*, BCancel, v) -> let refund u = "Refund " ++ show u ++ "\n" in (*, 0, refund v)
vend drink cost credit = if credit >= cost then (serve drink, credit - cost, *) else (*, credit, *);
serve drink = case drink of Coffee -> "Cofee\n" Tea -> "Tea\n"
box controlin (c :: char)out (coin :: Coins, button:: Buttons)match 'n' -> (Nickel, *) | 'd' -> (Dime, *) | 'c' -> (*, BCoffee) | 't' -> (*, BTea) | 'x' -> (*, BCancel) | _ -> (*, *)
stream console_outp to "std_out" ;stream console_inp from "std_in" ;
-- dataflow wiring
wire cofee -- inputs (channel origins) (control.coin, control.button, coffee.value’ initially 0) -- outputs destinations (console_outp, coffee.value, console_outp)
wire control (console_inp) (coffee.coin, coffee.button)
An extension of Visual Basic 9.0 with asynchronous concurrency constructs, called Concurrent Basic (for short CB), offer the join patterns. CB (builds on earlier work on Polyphonic C#, Cω and the Joins Library) adopts a simple event-like syntax familiar to VB programmers, allows one to declare generic concurrency abstractions and provides more natural support for inheritance, enabling a subclass to augment the set of patterns. CB class can declare method to execute when communication has occurred on a particular set of local channels asynchronous and synchronous, forming a join pattern.
Public Asynchronous Put(ByVal s As String) Public Synchronous Take As String
Private Function CaseTakeAndPut(ByVal s As String) As String _ When Take, Put Return s End Function
End ModuleThis example shows all new keywords used by Concurrent Basic: Asynchronous, Synchronous and When.[37]
This library is a high-level abstractions of the Join Pattern using objects and generics. Channels are special delegate values from some common Join object (instead of methods).[38]
The Scala Joins library uses the Join-Pattern. The pattern matching facilities of this language have been generalized to allow representation independence for objects used in pattern matching. So now it's possible to use a new type of abstraction in libraries. The advantage of join patterns is that they allow a declarative specification of the synchronization between different threads. Often, the join patterns corresponds closely to a finite state machine that specifies the valid states of the object.
In Scala, it's possible to solve many problem with the pattern matching and Scala Joins, for example the Reader-Writer.
With a class we declare events in regular fields. So, it's possible to use the Join construct to enable a pattern matching via a list of case declarations. That list is representing by => with on each side a part of the declaration. The left-side is a model of join pattern to show the combination of events asynchronous and synchronous and the right-side is the body of join which is executed with the join model is completed.
In Scala, it's also possible to use the Scala's actor library[40] with the join pattern. For example, an unbounded buffer:
Scala Join and Chymyst are newer implementations of the Join Pattern, improving upon Dr. Philipp Haller's Scala Joins.
Join Language is an implementation of the Join Pattern in Haskell.
The Join Patterns allows a new programming type especially for the multi-core architectures available in many programming situations with a high-levels of abstraction. This is based on the Guards and Propagation. So an example of this innovation has been implemented in Scheme .
Guards is essential to guarantee that only data with a matching key is updated/retrieved. Propagation can cancel an item, reads its contents and puts backs an item into a store. Of course, the item is also in the store during the reading. The guards is expressed with shared variables. And so the novelty is that the join pattern can contains now propagated and simplified parts. So in Scheme, the part before / is propagated and the part after / is removed.The use of the Goal-Based is to divise the work in many tasks and joins all results at the end with the join pattern. A system named "MiniJoin" has implemented to use the intermediate result to solve the others tasks if it's possible. If is not possible it waits the solution of others tasks to solve itself.
So the concurrent join pattern application executed in parallel on a multi-core architecture doesn't guarantee that parallel execution lead to conflicts. To Guarantee this and a high degree of parallelism, a Software Transactional Memory (STM) within a highlytuned concurrent data structure based on atomic compare-and-swap (CAS) is use. This allows to run many concurrents operations in parallel on multi-core architecture. Moreover, an atomic execution is used to prevent the "false conflict" between CAS and STM.
Join Pattern is not the only pattern to perform multitasks but it's the only one that allow communication between resources, synchronization and join different processes.