Does TAO support request/reply timeouts?
TAO supports the Relative Roundtrip Timeout policy as defined in the CORBA Messaging specification (OMG Document formal/04-03-12, Chapter 22). This policy allows you to specify the maximum time allowed (in 100 nanosecond units) for a request to be sent to and processed by a server and the reply received by the client. The policy can be applied at one of three levels: the client ORB, the requesting thread, or the object reference on which the request is invoked. Relative roundtrip timeouts can be applied when the client requires low request/reply latencies. The following example shows how to set the Relative Roundtrip Timeout policy to a value of 1 millisecond (that is 1.0e-3 * 1.
TAO supports the Relative Roundtrip Timeout policy as defined in the CORBA Messaging specification (OMG Document formal/04-03-12, Chapter 22). This policy allows you to specify the maximum time allowed (in 100 nanosecond units) for a request to be sent to and processed by a server and the reply received by the client. The policy can be applied at one of three levels: the client ORB, the requesting thread, or the object reference on which the request is invoked. Relative roundtrip timeouts can be applied when the client requires low request/reply latencies.