TAO_Reply_Dispatcher Class Reference

#include <Reply_Dispatcher.h>

Inheritance diagram for TAO_Reply_Dispatcher:

Inheritance graph

List of all members.

Public Member Functions

 TAO_Reply_Dispatcher (void)
virtual ~TAO_Reply_Dispatcher (void)
virtual int dispatch_reply (TAO_Pluggable_Reply_Params &params)=0
virtual void reply_timed_out (void)=0
 Inform that the reply timed out.
virtual void connection_closed (void)=0
GIOP::LocateStatusType locate_reply_status (void) const
 Get the locate reply status.
GIOP::ReplyStatusType reply_status (void) const

Protected Attributes

GIOP::LocateStatusType locate_reply_status_
 LocateReply status.
GIOP::ReplyStatusType reply_status_

Detailed Description

Different invocation modes process the Reply messages in different ways. Traditional synchronous replies simply receive the message and wake up the waiting thread (if any). Asynchronous Method Invocation (Callbacks) must process the message in the thread that receives it. Deferred Synchronous (DII) and AMI in the Poller mode save the reply for later processing in the application. The lower level components in the ORB only deal with this abstract interface, when the invocation is made the right type of Reply Dispatcher is instantiated and registered with the Transport object.

Constructor & Destructor Documentation

TAO_BEGIN_VERSIONED_NAMESPACE_DECL TAO_Reply_Dispatcher::TAO_Reply_Dispatcher ( void   ) 


TAO_Reply_Dispatcher::~TAO_Reply_Dispatcher ( void   )  [virtual]


Member Function Documentation

virtual int TAO_Reply_Dispatcher::dispatch_reply ( TAO_Pluggable_Reply_Params params  )  [pure virtual]

Dispatch the reply. Return 1 on sucess, -1 on error.

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_Synch_Reply_Dispatcher.

virtual void TAO_Reply_Dispatcher::reply_timed_out ( void   )  [pure virtual]

Inform that the reply timed out.

Implemented in TAO_Synch_Reply_Dispatcher.

virtual void TAO_Reply_Dispatcher::connection_closed ( void   )  [pure virtual]

The used for the pending reply has been closed. No reply is expected.

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_Synch_Reply_Dispatcher.

TAO_BEGIN_VERSIONED_NAMESPACE_DECL ACE_INLINE GIOP::LocateStatusType TAO_Reply_Dispatcher::locate_reply_status ( void   )  const

Get the locate reply status.

ACE_INLINE GIOP::ReplyStatusType TAO_Reply_Dispatcher::reply_status ( void   )  const

Member Data Documentation

GIOP::LocateStatusType TAO_Reply_Dispatcher::locate_reply_status_ [protected]

LocateReply status.

GIOP::ReplyStatusType TAO_Reply_Dispatcher::reply_status_ [protected]

The documentation for this class was generated from the following files:

Generated on Thu Nov 27 05:10:58 2008 for TAO by  doxygen 1.5.6