> >it's people realtime not real realtime. > > the former is an example of the latter. > real-time is meeting deadlines. deadlines are always real, if you've got them. > there isn't a distinction based on speed (ie, 1 usec is "real", but 10ms is > not). > any hard/soft distinction is typically based on whether the program can miss > a deadline, > and the consequences.
my point was that the consequences for occassional misses are just a reduced perception of responsiveness. for most applications, this should be okay. i would think it would be an undue burden to break out the realtime tools for any program that has a ui. (not related to my point, what about a time frame of 1 minute? one day?) - erik
