Originally Posted by LinuxInfo
What kind of applications can be considedred as Hard-Real time and what kind of applications cab be considred as Soft-Real time.
To add to what salasi has already posted, this question really doesn't make sense. The vast majority of applications are not real-time at all. Even when working with a real-time system, "does this particular job require real-time processing" is not even the first question you ask; you start from questions such as "what are the tolerable latencies" and "can I miss some small amounts of data or must it absolutely all be processed" and from there a multitude of other questions come up. Come to think of it, in my experience the question "do we need a real time kernel" has never come up. However, in working out the requirements for a particular job it has sometimes been concluded that a real-time kernel is essential. The decision to use a real-time kernel comes from the analysis of the requirements, examination of the proposed system, expected and measured latencies, and a number of other factors.
Use of real-time systems often (but not always) comes up in signal measurement systems.
In my experience when someone says "I need a real-time system", over 90% of the time they don't know what they're talking about and in fact do not need a real-time system. (Maybe one day I'll be exposed to more intelligent people.) There is no simple rule for determining whether you do or don't need a real-time system.
SO - if you want examples of real-time programs, you'll simply have to scour the internet for those examples. Odds are even among the "real-time" programs you find, many of them will not really have a "real-time" requirement and would work just as well on an ordinary system with the stock scheduler and even under moderate to high CPU loading. That is why the question about what real-time programs are out there really makes little sense.