It could also allow applications using the middleware access to the real-time features of the underlying infrastructure. Both of these alternatives are currently under consideration or development. The current OMG Realtime RFP includes the potential for establishing communications using real-time protocols. Clearly a real-time API is more in the spirit of middleware by providing a common abstraction. Providing access to operations of the underlying infrastructure allows the ultimate in control over infrastructure features not typically recognized by the middleware.
Further research is needed to evaluate the tradeoffs of both approaches.
Benefits must be weighed not only with respect to current technologies and real-time applications but with regard to expected evolutionary paths of emerging technologies. The new generation of real-time applications will frequently not have this luxury. Some way of resolving this conflict is necessary to achieve the desired componentware markets envisioned as a result of these efforts. The coming distributed infrastructure must support real-time computing by providing the necessary bridge between current practice and future need. Optimal Scheduling and Handling Potential Overload.