Synch_Invocation.cpp File Reference

#include "tao/Synch_Invocation.h"
#include "tao/Profile_Transport_Resolver.h"
#include "tao/Profile.h"
#include "tao/Synch_Reply_Dispatcher.h"
#include "tao/Transport.h"
#include "tao/Stub.h"
#include "tao/Bind_Dispatcher_Guard.h"
#include "tao/operation_details.h"
#include "tao/Wait_Strategy.h"
#include "tao/debug.h"
#include "tao/ORB_Constants.h"
#include "tao/Messaging_SyncScopeC.h"
#include "tao/ORB_Core.h"
#include "tao/Service_Context.h"
#include "tao/SystemException.h"
#include "ace/Intrusive_Auto_Ptr.h"
#include "tao/PortableInterceptorC.h"
#include "ace/Auto_Ptr.h"
#include "ace/OS_NS_string.h"
#include "ace/Countdown_Time.h"
Include dependency graph for Synch_Invocation.cpp:

Functions

 ACE_RCSID (tao, Synch_Invocation,"$Id: Synch_Invocation.cpp 86232 2009-07-24 21:52:20Z dai_y $") 1 namespace TAO

Function Documentation

ACE_RCSID ( tao  ,
Synch_Invocation  ,
"$Id: Synch_Invocation.cpp 86232 2009-07-24 21:52:20Z dai_y $"   
)

There has been a unanimous view that this is not the right way to do things. But a need to be compliant is forcing us into this.

Note:
A location forwarding loop may occur where a client is bounced from the original target to the forwarded target and back if the application is not equipped to handle retries of previously called targets. TAO may be able to help in this case but it ultimately ends up being an application issue.

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Friends Defines

Generated on Fri Sep 11 04:07:34 2009 for TAO by  doxygen 1.6.1