2016
DOI: 10.1016/j.scico.2015.10.006
|View full text |Cite
|
Sign up to set email alerts
|

Parameterized, concurrent session types for asynchronous multi-actor interactions

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
12
0

Year Published

2017
2017
2024
2024

Publication Types

Select...
5
3
1

Relationship

1
8

Authors

Journals

citations
Cited by 19 publications
(13 citation statements)
references
References 16 publications
0
12
0
Order By: Relevance
“…Our approach using slots to deal with simultaneous multiple sessions resembles parameterised session types [41,42], and it is smoothly extendable to the multiparty session type framework [43]. For future work, we plan to investigate code generations from Scribble [44] (a protocol description language for the multiparty session types) along the line of [13,12] integrating session-ocaml with parameterised features [41,42].…”
Section: Resultsmentioning
confidence: 99%
“…Our approach using slots to deal with simultaneous multiple sessions resembles parameterised session types [41,42], and it is smoothly extendable to the multiparty session type framework [43]. For future work, we plan to investigate code generations from Scribble [44] (a protocol description language for the multiparty session types) along the line of [13,12] integrating session-ocaml with parameterised features [41,42].…”
Section: Resultsmentioning
confidence: 99%
“…In general, the programmers of individual endpoints in a modular development of some non-trivial multiparty application (e.g., not just binary RPCs) should commence development top-down from some notion of agreed protocolÐotherwise the separate programmers cannot locally determine the (inherently stateful) I/O structure that their endpoint should implement. Charalambides et al [2016] extend MPST theory with parameterised versions of session type operators that represent repeat applications of the operator for some parameter value (possibly run-time instantiated). Unlike our work, their system does not support role-parametric protocols as their approach expressly requires prohibiting separate occurrences of a role with different indices; this rules out, e.g., role-parametric pipeline structures.…”
Section: Related Workmentioning
confidence: 99%
“…[Lange et al 2018] infers behavioural types from Go source code and uses a model checker to analyse safety and liveness properties. Session Types [Charalambides et al 2016;Deniélou et al 2012;Honda 1993;Honda et al 2012Honda et al , 2008Lange et al 2018] project a user-provided global protocol into a set of types for the various local processes of a program. Unlike us, however, they require the user to specify the global protocol and are not concerned with functional correctness.…”
Section: Related Workmentioning
confidence: 99%