2010
DOI: 10.1007/978-3-642-13414-2_5
|View full text |Cite
|
Sign up to set email alerts
|

JErlang: Erlang with Joins

Abstract: Abstract.Erlang is an industrially successful functional language that uses the Actor model for concurrency. It supports the messagepassing paradigm by providing pattern-matching over received messages. Unfortunately coding synchronisation between multiple processes is not straightforward. To overcome this limitation we designed and implemented JErlang, a Join-Calculus inspired extension to Erlang. We provide a rich set of language features with our joins. We present implementation details of our two alternati… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
28
0

Year Published

2010
2010
2019
2019

Publication Types

Select...
6
3

Relationship

0
9

Authors

Journals

citations
Cited by 25 publications
(28 citation statements)
references
References 10 publications
0
28
0
Order By: Relevance
“…Finally, JErlang [25] extends the Erlang actor-based concurrency model. Channels are messages exchanged by actors, and received patterns are extended to express matching of multiple subsequent messages.…”
Section: Formal Calculi For Concurrent and Distributed Servicesmentioning
confidence: 99%
“…Finally, JErlang [25] extends the Erlang actor-based concurrency model. Channels are messages exchanged by actors, and received patterns are extended to express matching of multiple subsequent messages.…”
Section: Formal Calculi For Concurrent and Distributed Servicesmentioning
confidence: 99%
“…None of these provide any other features than propagation of implicit invocations; focusing on centralized deployments, Ptolemy or EScala could easily provide information on the number of publishers per subscriber or vice-versa. In contrast, languages based on Actors (e.g., Erlang [12]) and inspired by the Join Calculus [18] (e.g., Polyphonic C# [2]-now integrated with C#), or combining the two (e.g., Scala Actors [22], Erlang Joins [44,37]) focus on asynchronous invocations on single destinations, and thus do not support implicit invocations.…”
Section: Implicit Invocationsmentioning
confidence: 99%
“…Given that processes can publish their states as events, modern Complex Event Processing languages (e.g., [21]) can express conditions on network context using event correlation and predicates. However, representation of external data retrieved from request-response web APIs in the form of events is not intuitive.…”
Section: Related Workmentioning
confidence: 99%