Linked by Thom Holwerda on Mon 16th Apr 2007 20:56 UTC, submitted by BlueVoodoo
"This article, the first in a five-part series on real-time Java, describes the key challenges to using the Java language to develop systems that meet real-time performance requirements. It presents a broad overview of what real-time application development means and how runtime systems must be engineered to meet the requirements of real-time applications. The authors introduce an implementation that addresses real-time Java challenges through a combination of standards-based technologies."
Thread beginning with comment 231585
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-24
"""
What it means to be an RT application depends in large part on how tolerant the application can be to faults in the form of missed timing requirements.
"""
Perhaps some descriptions of different kinds of real time applications would help.
If the software operating the controls can miss an event and the result would be that the airplane would only *nearly* crash, or the reactor core would only *nearly* melt down, then that is soft real time.
But if the microprocessor in your convection oven fails to turn the oven off at exactly the right time, and as a result, you totally miss getting grand prize at the bake-off, then that is a hard real time application.
Opinions may differ, depending upon whether one is on the plane or at the bake-off.
Edited 2007-04-17 14:50