Product: OpenFusion TAO
Version: ALL

Description:

How does TAO implement the processing of oneway requests?

Solution: 

TAO implements one way requests in exactly the same way as a two way requests. The client thread leaves the application code, connects a socket to the server, and writes the GIOP header and message to the socket - so far exactly the same as a two way call. It then returns directly to the application code.

A two way call would put the thread into the reactor or block in recv on the socket (depending on the client connection policy) until the server returned a GIOP response to say that the request was completed.

It is possible for TAO oneway requests to arrive out of order or not at all (depending on the policy used). This behavior is defined in the CORBA specification.