2010
DOI: 10.1109/tpds.2009.95
|View full text |Cite
|
Sign up to set email alerts
|

A Synchronous Scheduling Service for Distributed Real-Time Java

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
29
0

Year Published

2010
2010
2012
2012

Publication Types

Select...
6
1
1

Relationship

2
6

Authors

Journals

citations
Cited by 22 publications
(29 citation statements)
references
References 27 publications
0
29
0
Order By: Relevance
“…It is necessary in that system to define the mechanisms of selection of components, application composition and a distributed scheduling to allow the development of fully distributed applications. Current distributed real-time Java technology has not addressed reconfiguration based on SOA [43], although some mechanisms proposed by the authors can be useful as a basic support for dynamic reconfiguration [44][45][46][47].…”
Section: Introductionmentioning
confidence: 99%
“…It is necessary in that system to define the mechanisms of selection of components, application composition and a distributed scheduling to allow the development of fully distributed applications. Current distributed real-time Java technology has not addressed reconfiguration based on SOA [43], although some mechanisms proposed by the authors can be useful as a basic support for dynamic reconfiguration [44][45][46][47].…”
Section: Introductionmentioning
confidence: 99%
“…The second important result refers to the case with several handlers subscribed [i.e., D.E(4) and D.E (16)]. There is a linear relationship among the number of subscribers and the blocking experienced at the server, as suggested by the model proposed in Section III, which is supported by the empirical evidence.…”
Section: A Performance Patternsmentioning
confidence: 65%
“…NTP). For instance, in the Synchronous Scheduling Service (SSS) [16] of DREQUIEMI, S-choreographies execute a synchronization protocol between the master and its corresponding slaves. Depending on the quality of the infrastructure the jitter may be around ±100 µs in most cases (a performance similar to the second option).…”
Section: ) Time Synchrnonizationmentioning
confidence: 99%