TAO
2.2.2
|
Encapsulate the flushing control parameters. More...
#include <Transport.h>
Public Member Functions | |
Drain_Constraints () | |
Default constructor. More... | |
Drain_Constraints (ACE_Time_Value *timeout, bool block_on_io) | |
Constructor. More... | |
bool | block_on_io () const |
ACE_Time_Value * | timeout () const |
Private Attributes | |
ACE_Time_Value * | timeout_ |
bool | block_on_io_ |
Encapsulate the flushing control parameters.
At several points, the ORB needs to flush data from a transport to the underlying I/O mechanisms. How this data is flushed depends on the context where the request is made, the ORB configuration and the application level policies in effect.
Some examples:
space available. In this case, the queue must be drained on a best-effort basis, without any blocking.
request should block and push data to the underlying socket as fast as possible.
effect, the ORB will need to send the data use I/O operations with timeouts (as implemented by ACE::sendv()
reliable oneway or similar should wait using the reactor or Leader-Follower implementation. While still respecting the timeout policies.
Instead of sprinkling if() statements throughput the critical path trying to determine how the I/O operations should be performed, we pass the information encapsulated in this class. The caller into the Transport object determines the right parameters to use, and the Transport object simply obeys those instructions.
|
inline |
Default constructor.
|
inline |
Constructor.
|
inline |
If true, then the ORB should block on I/O operations instead of using non-blocking I/O.
|
inline |
The maximum time to block on I/O operations (or nested loops) based on the current timeout policies.
|
private |
|
private |