TAO_Muxed_TMS Class Reference#include <Muxed_TMS.h>
Inheritance diagram for TAO_Muxed_TMS:
Collaboration diagram for TAO_Muxed_TMS:
Detailed DescriptionUsing 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?
Member Typedef Documentation
Constructor & Destructor Documentation
Constructor.
Destructor.
Member Function Documentation
Generate and return an unique request id for the current invocation. Implements TAO_Transport_Mux_Strategy.
Unbind the dispatcher, the client is no longer waiting for the request, for example, because the request timedout. 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.
Dispatch the reply for <request_id>, cleanup any resources allocated for that request. Implements TAO_Transport_Mux_Strategy.
Dispatch a reply timeout for request request_id Implements TAO_Transport_Mux_Strategy.
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.
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.
The transport object has closed the connection, inform all Reply dispatchers and waiting strategies. Implements TAO_Transport_Mux_Strategy.
Member Data Documentation
Lock to protect the state of the object.
Used to generate a different request_id on each call to request_id().
Keep track of the orb core pointer. We need to this to create the Reply Dispatchers. Table of <Request ID, Reply Dispatcher> pairs.
The documentation for this class was generated from the following files: Generated on Mon Sep 15 07:41:33 2008 for TAO by 1.5.5 |