2011
DOI: 10.1002/cpe.1756
|View full text |Cite
|
Sign up to set email alerts
|

Asynchronous event handling and Safety Critical Java

Abstract: SUMMARY Over the last few years, the Java Community Process (under the auspices of Java Specification Request 302) has been developing a subset of Java augmented by the Real‐Time Specification for Java (RTSJ) for use in safety critical systems. The concurrency model supported by Safety Critical Java (SCJ) relies almost exclusively on an event‐based model rather than on a thread‐based model. This paper reviews the advantages and disadvantages of the two models and gives the pragmatic reasons that SCJ has adopte… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
2
0

Year Published

2011
2011
2013
2013

Publication Types

Select...
2
1

Relationship

1
2

Authors

Journals

citations
Cited by 3 publications
(2 citation statements)
references
References 19 publications
0
2
0
Order By: Relevance
“…SCJ supports the notion of missions; a good introduction to this is given by Hunt and Nilsen [13]. The concurrency model is based on event handlers -see Wellings and Kim [24] for a rationale for this approach. Ravenscar Ada is a highly restricted subset of the full Ada concurrency and real-time models; see Burns [4] for the initial specification, and Burns and Wellings [3] for full consideration.…”
Section: Introductionmentioning
confidence: 99%
“…SCJ supports the notion of missions; a good introduction to this is given by Hunt and Nilsen [13]. The concurrency model is based on event handlers -see Wellings and Kim [24] for a rationale for this approach. Ravenscar Ada is a highly restricted subset of the full Ada concurrency and real-time models; see Burns [4] for the initial specification, and Burns and Wellings [3] for full consideration.…”
Section: Introductionmentioning
confidence: 99%
“…The SCJ has been designed only with the abstraction of an event handler, however, with a close correspondence to threads. The motivations for this decision are analyzed in detail in the fourth paper of this issue, by Wellings and Kim . The paper proposes a cleaner API for handlers that removes confusions with the use of bound event handlers and that allows optimizations of thread mappings.…”
mentioning
confidence: 99%