Table 1: Real-time CORBA features
| Design Challenge | Example from Application | Real-time CORBA Feature |
| Configuring custom protocols to obtain adequate end-to-end network-level QoS. | TCP/IP is inadequate to provide end-to-end real-time response, so communication between application objects must use a different protocol. | Use the Real-time CORBA ClientProtocol and ServerProtocol policies to select and/or configure the necessary network protocols. |
| Controlling network and end system resources to minimize priority inversion. | High-priority operations, such as edge_alarm or stop, must not be queued behind low-priority operations, such as query_state. | Use the Real-time CORBA PriorityBandedConnectionPolicy to associate different connections with different thread priority ranges. |
| Avoiding dynamic connections since the jitter is detrimental to time-critical operations. | Connections must be established explicitly between the base station and the drones to avoid unacceptable jitter. | Pre-allocate one or more connections via the Object::_validate_connection operation. |
| Minimizing priority inversions by ensuring applications don't share a connection between threads running at different priorities. | High-priority operations, such as edge_alarm or stop, need to use exclusive, pre-allocated connections to avoid "head-of-line" blocking. | Use the Real-time CORBA PrivateConnectionPolicy to ensure the use of non-multiplexed connections. |
