TAO_Synch_Queued_Message Class ReferenceSpecialize TAO_Queued_Message for synchronous requests, i.e. twoways and oneways sent with reliability better than SYNC_NONE. More...
Inheritance diagram for TAO_Synch_Queued_Message:
Collaboration diagram for TAO_Synch_Queued_Message:
Detailed DescriptionSpecialize TAO_Queued_Message for synchronous requests, i.e. twoways and oneways sent with reliability better than SYNC_NONE.Reliable requests block the sending thread until the message is sent, likewise, the sending thread must be informed if the connection is closed or the message times out. In contrast oneway (and AMI) requests sent with the SYNC_NONE policy are simple discarded if the connection fails or they timeout. Another important difference is the management of the data buffer: one SYNC_NONE messages the buffer is immediately copied into a newly allocated buffer, and must be deallocated. Other types of requests use the memory allocated by the sending thread. Constructor & Destructor Documentation
Constructor.
Destructor.
Member Function Documentation
Return the length of the message. If the message has been partially sent it returns the number of bytes that are still not sent. Implements TAO_Queued_Message.
Fill up an io vector using the connects of the message. Different versions of this class represent the message using either a single buffer, or a message block. This method allows a derived class to fill up the contents of an io vector, the TAO_Transport class uses this method to group as many messages as possible in an iovector before sending them to the OS I/O subsystem.
Implements TAO_Queued_Message.
Update the internal state, data has been sent. After the TAO_Transport class completes a successful (or partially successful) I/O operation it must update the state of all the messages queued. This callback method is used by each message to update its state and determine if all the data has been sent already.
Implements TAO_Queued_Message.
Reclaim resources. Reliable messages are allocated from the stack, thus they do not be deallocated. Asynchronous (SYNC_NONE) messages are allocated from the heap (or a pool), they need to be reclaimed explicitly. Implements TAO_Queued_Message.
Provide a hook for copying the underlying data.
Implements TAO_Queued_Message.
Member Data DocumentationThe contents of the message. The message is normally generated by a TAO_OutputCDR stream. The application marshals the payload, possibly generating a chain of message block connected via the 'cont()' field. The current message block. The message may be set in multiple writev() operations. This point keeps track of the next message to send out.
Do we own the contents_ message block? This flag differs from the is_heap_allocated_ flag in that it only applies to the contents_ message block and not the TAO_Synch_Queued_Message object itself.
The documentation for this class was generated from the following files: Generated on Mon Sep 15 07:42:41 2008 for TAO by 1.5.5 |