#include <Reply_Dispatcher.h>
Inheritance diagram for TAO_Reply_Dispatcher:

Public Methods | |
| TAO_Reply_Dispatcher (void) | |
| Constructor. | |
| virtual | ~TAO_Reply_Dispatcher (void) |
| Destructor. | |
| virtual int | dispatch_reply (TAO_Pluggable_Reply_Params ¶ms)=0 |
| virtual void | connection_closed (void)=0 |
| CORBA::ULong | reply_status (void) const |
| Get the reply status. | |
Protected Attributes | |
| CORBA::ULong | reply_status_ |
| Reply or LocateReply status. | |
|
|
Constructor.
|
|
|
Destructor.
|
|
|
The used for the pending reply has been closed. No reply is expected. @ TODO: If the connection was closed due to a CloseConnection message then we could re-issue the request instead of raising the exception, it would a matter of simply adding a boolean argument to this function. Implemented in TAO_Asynch_Reply_Dispatcher_Base, and TAO_Synch_Reply_Dispatcher. |
|
|
Dispatch the reply. Return 1 on sucess, -1 on error. @ TODO Pluggable Messaging: this method has too many arguments, the "Right Thing"[tm] is for the Transport Object to create a "ClientReply" that encapsulates all we need to process a reply. Naturally it is possible that different messaging protocols implement different variants of such ClientReply class. Implemented in TAO_Asynch_Reply_Dispatcher_Base, and TAO_Synch_Reply_Dispatcher. |
|
|
Get the reply status.
|
|
|
Reply or LocateReply status.
|
1.2.18