TAO
2.1.1
|
#include <Muxed_TMS.h>
Using this strategy a single connection can have multiple outstanding requests. @ Can the performance of the demuxer be made more predictable, for example, using the request id as an active demux key?
TAO_Muxed_TMS::TAO_Muxed_TMS | ( | TAO_Transport * | transport | ) |
Constructor.
|
virtual |
Destructor.
|
private |
|
virtual |
Bind the dispatcher with the request id.
Implements TAO_Transport_Mux_Strategy.
|
private |
|
virtual |
The transport object has closed the connection, inform all Reply dispatchers and waiting strategies.
Implements TAO_Transport_Mux_Strategy.
|
virtual |
Dispatch the reply for request_id, cleanup any resources allocated for that request.
Implements TAO_Transport_Mux_Strategy.
|
virtual |
Do we have a request pending.
Implements TAO_Transport_Mux_Strategy.
|
virtual |
Request is sent and the reply is received. Idle the transport now. The return value indicates whether idling was successful or not.
Implements TAO_Transport_Mux_Strategy.
|
virtual |
Request has been just sent, but the reply is not received. Idle the transport now. The return value indicates whether idling was successful or not.
Implements TAO_Transport_Mux_Strategy.
|
private |
|
virtual |
Dispatch a reply timeout for request request_id
Implements TAO_Transport_Mux_Strategy.
|
virtual |
Generate and return an unique request id for the current invocation.
Implements TAO_Transport_Mux_Strategy.
|
virtual |
Unbind the dispatcher, the client is no longer waiting for the request, for example, because the request timed out. The strategy can (must) cleanup any resources associated with the request. A later reply for that request should be ignored.
Implements TAO_Transport_Mux_Strategy.
Table of <Request ID, Reply Dispatcher> pairs.
|
private |
Lock to protect the state of the object.
|
private |
Keep track of the orb core pointer. We need to this to create the Reply Dispatchers.
Used to generate a different request_id on each call to request_id().