Service_Config.cpp File Reference

#include "ace/Service_Config.h"
#include "ace/Service_Types.h"
#include "ace/Reactor.h"
#include "ace/Singleton.h"
#include "ace/Service_Repository.h"
#include "ace/Sig_Adapter.h"
#include "ace/OS_NS_time.h"
#include "ace/OS_NS_stdio.h"
#include "ace/OS_NS_unistd.h"
#include "ace/Thread.h"
#include "ace/Get_Opt.h"
#include "ace/ARGV.h"
#include "ace/Log_Msg.h"
#include "ace/ACE.h"

Include dependency graph for Service_Config.cpp:

Typedefs
typedef ACE_Unmanaged_Singleton < ACE_Service_Config, ACE_SYNCH_RECURSIVE_MUTEX >	ACE_SERVICE_CONFIG_SINGLETON
Functions
	ACE_RCSID (ace, Service_Config,"$Id: Service_Config.cpp 84619 2009-02-26 12:26:16Z johnnyw $") 1 ACE_Threading_Helper< ACE_Thread_Mutex >

---

Typedef Documentation

typedef ACE_Unmanaged_Singleton<ACE_Service_Config, ACE_SYNCH_RECURSIVE_MUTEX> ACE_SERVICE_CONFIG_SINGLETON

ACE_Service_Config is supposed to be a Singleton. This is the only Configuration Gestalt available for access from static initializers at proces start-up time. Using Unmanaged Singleton is safer because (a) the Object Manager may not yet be fully initialized in the context of a static initializer that uses SC, and (b) because we know that upon process exit the SC will still be automaticaly and explicitly closed by ACE_Object_Manager::fini().

---

Function Documentation

ACE_RCSID	(	ace	,
		Service_Config	,
		"$Id: Service_Config.cpp 84619 2009-02-26 12:26:16Z johnnyw $"
	)