#include <GIOP_Message_Base.h>
Inheritance diagram for TAO_GIOP_Message_Base:
This class will hold the specific details common to all the GIOP versions. Some of them which are here may be shifted if things start changing between versions. This class uses the TAO_GIOP_Message_Reactive_Handler to read and parse messages.
|
Constructor.
|
|
Dtor.
|
|
Bala:Docu?? @ Implements TAO_Pluggable_Messaging. |
|
Check whether the node <qd> needs consolidation from <incoming>.
Implements TAO_Pluggable_Messaging. |
|
Print out a debug messages..
|
|
Implements TAO_Pluggable_Messaging. |
|
Format the message. As we have not written the message length in the header, we make use of this oppurtunity to insert and format the message. Implements TAO_Pluggable_Messaging. |
|
Generate a reply message with the exception <ex>.
Implements TAO_Pluggable_Messaging. |
|
Write the locate reply header.
Implements TAO_Pluggable_Messaging. |
|
Write the RequestHeader in to the <cdr> stream.
Implements TAO_Pluggable_Messaging. |
|
Write the reply header.
Implements TAO_Pluggable_Messaging. |
|
Write the RequestHeader in to the <cdr> stream. The underlying implementation of the mesaging should do the right thing. Implements TAO_Pluggable_Messaging. |
|
Get the details of the message parsed through the <qd>.
Implements TAO_Pluggable_Messaging. |
|
Header length.
Implements TAO_Pluggable_Messaging. |
|
Initialize the underlying state object based on the <major> and <minor> revision numbers Implements TAO_Pluggable_Messaging. |
|
Is the messaging object ready for processing BiDirectional request/response? Implements TAO_Pluggable_Messaging. |
|
Creates a new node for the queue with a message block in the node of size <sz>.. |
|
Make a <GIOP_LOCATEREPLY> and hand that over to the transport so that it can be sent over the connection. NOTE:As on date 1.1 & 1.2 seem to have similar headers. Till an unmanageable difference comes let them be implemented here. |
|
Get the message type. The return value would be one of the following: TAO_PLUGGABLE_MESSAGE_REQUEST, TAO_PLUGGABLE_MESSAGE_REPLY, TAO_PLUGGABLE_MESSAGE_CLOSECONNECTION, TAO_PLUGGABLE_MESSAGE_MESSAGE_ERROR. |
|
Calculate the amount of data that is missing in the <incoming> message block. Implements TAO_Pluggable_Messaging. |
|
Accessor for the output CDR stream.
Implements TAO_Pluggable_Messaging. |
|
Parse the incoming messages..
Implements TAO_Pluggable_Messaging. |
|
Processes the <GIOP_LOCATE_REQUEST> messages.
|
|
Parse the reply message that we received and return the reply information though <reply_info> Implements TAO_Pluggable_Messaging. |
|
Processes the <GIOP_REQUEST> messages.
|
|
Process the request message that we have received on the connection Implements TAO_Pluggable_Messaging. |
|
This method reads the message on the connection. Returns 0 when there is short read on the connection. Returns 1 when the full message is read and handled. Returns -1 on errors. If <block> is 1, then reply is read in a blocking manner. Implements TAO_Pluggable_Messaging. |
|
Reset the messaging the object.
Implements TAO_Pluggable_Messaging. |
|
Close a connection, first sending GIOP::CloseConnection.
|
|
Send error messages.
|
|
We must send a LocateReply through <transport>, this request resulted in some kind of exception. |
|
Set the state.
|
|
Writes the GIOP header in to <msg> NOTE: If the GIOP header happens to change in the future, we can push this method in to the generator_parser classes. |
|
The generator and parser state. Buffer used for both the output and input CDR streams, this is "safe" because we only one of the streams at a time. |
|
Thr message handler object that does reading and parsing of the incoming messages |
|
Cached ORB_Core pointer...
|
|
Buffer where the request is placed.
|
|
All the implementations of GIOP message generator and parsers.
|