#include <Resume_Handle.h>
Collaboration diagram for TAO_Resume_Handle:
Public Types | |
enum | TAO_Handle_Resume_Flag { TAO_HANDLE_RESUMABLE = 0, TAO_HANDLE_ALREADY_RESUMED, TAO_HANDLE_LEAVE_SUSPENDED } |
Public Member Functions | |
TAO_Resume_Handle (TAO_ORB_Core *orb_core=0, ACE_HANDLE h=ACE_INVALID_HANDLE) | |
Ctor. | |
~TAO_Resume_Handle (void) | |
Dtor. | |
void | set_flag (TAO_Handle_Resume_Flag fl) |
Allow the users of this class to change the underlying flag. | |
TAO_Resume_Handle & | operator= (const TAO_Resume_Handle &rhs) |
Equal to operator.. | |
void | resume_handle (void) |
Private Attributes | |
TAO_ORB_Core * | orb_core_ |
Our ORB Core. | |
ACE_HANDLE | handle_ |
The actual handle that needs resumption.. | |
TAO_Handle_Resume_Flag | flag_ |
Please read the documentation in the bugzilla #575 in the bugzilla database what we mean by handler resumption.
When TAO uses a TP reactor, it takes care of resuming the handler once it makes sure that it has read the whole message out of the socket. During the process of reading the transport object would have to deal with errors in 'read' from the socket, or errors in the messages that has been received. Instead of calling resume_handler () on the reactor at every point in the code, we use this utility class to take care of the resumption.
|
|
|
Ctor.
|
|
Dtor.
|
|
Equal to operator..
|
|
Resume the handle in the reactor only if the ORB uses a TP reactor. Else we dont resume the handle. |
|
Allow the users of this class to change the underlying flag.
|
|
The flag for indicating whether the handle has been resumed or not. A value of '0' indicates that the handle needs resumption. |
|
The actual handle that needs resumption..
|
|
Our ORB Core.
|