#include <Pluggable_Messaging.h>
Inheritance diagram for TAO_Pluggable_Messaging:
This interface tries to define generic methods that could be different messaging protocols
|
Dtor.
|
|
Consolidate newly received fragment with previously arrived associated fragments to achieve consolidated message. All fragments having been received previously are being managed within implementation. If reliable transport is used (like TCP) this operation will be invoked with fragments being received partially ordered, last fragment being received last. Otherwise If un-reliable transport is used (like UDP) fragments may be received dis-ordered, and must be ordered before consolidation within implementation.
Implemented in TAO_GIOP_Message_Base, and TAO_GIOP_Message_Lite. |
|
Check whether the node qd needs consolidation from incoming, 0 on success, -1 on error Implemented in TAO_GIOP_Message_Base, and TAO_GIOP_Message_Lite. |
|
Discard all fragments associated to request-id encoded in cancel_request. Transport implementaion guarantees that this operation will never be invoked // concurrently by multiplpe threads nor concurrently to consolidate_fragmented_message
Implemented in TAO_GIOP_Message_Base, and TAO_GIOP_Message_Lite. |
|
Extract the details of the next message from the incoming through qd. Returns 0 if the message header could not be parsed completely, returns a 1 if the message header could be parsed completely and returns -1 on error. Implemented in TAO_GIOP_Message_Base, and TAO_GIOP_Message_Lite. |
|
Format the message in the cdr. May not be needed in general. Implemented in TAO_GIOP_Message_Base, and TAO_GIOP_Message_Lite. |
|
Fragment header length.
Implemented in TAO_GIOP_Message_Base, and TAO_GIOP_Message_Lite. |
|
Generate a reply message with the exception ex.
Implemented in TAO_GIOP_Message_Base, and TAO_GIOP_Message_Lite. |
|
Write the locate reply header The locate reply header is a part of any messaging protocol. The messaging protocol implementation would implement the way the locate reply header is written. Implemented in TAO_GIOP_Message_Base, and TAO_GIOP_Message_Lite. |
|
Write the RequestHeader in to the cdr stream.
Implemented in TAO_GIOP_Message_Base, and TAO_GIOP_Message_Lite. |
|
Write the reply header The reply header is a part of any messaging protocol. The messaging protocol implementation would implement the way the reply header is written. Implemented in TAO_GIOP_Message_Base, and TAO_GIOP_Message_Lite. |
|
Write the RequestHeader in to the cdr stream. The underlying implementation of the mesaging should do the right thing. Implemented in TAO_GIOP_Message_Base, and TAO_GIOP_Message_Lite. |
|
Header length.
Implemented in TAO_GIOP_Message_Base, and TAO_GIOP_Message_Lite. |
|
Do any initialisations that may be needed.
Implemented in TAO_GIOP_Message_Base, and TAO_GIOP_Message_Lite. |
|
Is the messaging object ready for processing BiDirectional request/response? Implemented in TAO_GIOP_Message_Base, and TAO_GIOP_Message_Lite. |
|
Accessor for the output CDR stream.
Implemented in TAO_GIOP_Message_Base, and TAO_GIOP_Message_Lite. |
|
Parse the details of the next message from the incoming and initializes attributes of qd. Returns 0 if the message header could not be parsed completely, returns a 1 if the message header could be parsed completely and returns -1 on error. As the parsed data is stored directly in qd, no state must be stored in instance of implementation. Implemented in TAO_GIOP_Message_Base, and TAO_GIOP_Message_Lite. |
|
Parse the reply message that we received and return the reply information through reply_info Implemented in TAO_GIOP_Message_Base, and TAO_GIOP_Message_Lite. |
|
Parse the request message, make an upcall and send the reply back to the "request initiator" Implemented in TAO_GIOP_Message_Base, and TAO_GIOP_Message_Lite. |
|
Reset the messaging the object.
Implemented in TAO_GIOP_Message_Base, and TAO_GIOP_Message_Lite. |