Linked by Thom Holwerda on Mon 16th Apr 2007 20:56 UTC, submitted by BlueVoodoo
Java "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 231484
To read all comments associated with this story, please click here.
Not the first word that comes to mind...
by jasutton on Tue 17th Apr 2007 03:34 UTC
Member since:

Real-time wouldn't be the first word I think of when I think Java. In fact, "slow" would be the first word. Now, before I get a bunch of Java developers flaming me for making the same generalization that people have been making for years, I want to point out that it is just the first word that comes to mind for me. I understand that Java has improved immensely over the last several releases, and I applaud Sun for that.

However, even today, Java applications (the first two widely-used apps that come to mind are Eclipse SDK and Azureus) have a hard time keeping up with user interface demands (what the article calls "soft Real Time applications"). So, if that's the case, why would I want to trust Java with my airplane rudder (an example the article uses to describe a "hard real time application")?

Reply Score: 2

Soulbender Member since:

"Real-time wouldn't be the first word I think of when I think Java. In fact, "slow" would be the first word."

Real-time != speed.

Reply Parent Score: 3

Laurence Member since:


Real-time != speed.

That really depends on the specification of the RT application (ie whether it's hard-RT or soft-RT)

To quote the article posted:

"Real-time (RT) is a broad term used to describe applications that have real-world timing requirements. For example, a sluggish user interface doesn't satisfy an average user's generic RT requirements. This type of application is often described as a soft RT application. The same requirement might be more explicitly phrased as "the application should not take more than 0.1 seconds to respond to a mouse click." If the requirement isn't met, it's a soft failure: the application can continue, and the user, though unhappy, can still use it. In contrast, applications that must strictly meet real-world timing requirements are typically called hard RT applications. An application controlling the rudder of an airplane, for example, must not be delayed for any reason because the result could be catastrophic. 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. "

Taking this into account, I think jasutton's point is more than valid.

Edited 2007-04-17 11:00

Reply Parent Score: 2