22.6 Async Operation Mapping

   For each operation in an interface, corresponding callback and polling asynchronous method signatures are generated. These signatures are described in implied-IDL, which is used to generate language-specific operation signatures. The implementation of these methods may generate a method invocation as described in Section 22.14, “Message Routing,? on page 22-45, depending on the effective RoutingPolicy for the invocation. Note that these generated operations are not included in the interface’s definition (CORBA::InterfaceDef). These operations do not raise user exceptions. Just as with the currently specified CORBA::Request::send operation, they can (but are not required to) raise system exceptions. For explanatory purposes, the sections below show the Callback and Polling implied-IDL in separate pieces. Logically, the IDL compiler deals with async as if the IDL included all three pieces: the original IDL and the implied IDL for both async models.