OpenDDS::DCPS::DataDurabilityCache Class Reference

Underlying data cache for both OpenDDS TRANSIENT and PERSISTENT DURABILITY implementations.. More...

#include <DataDurabilityCache.h>

Collaboration diagram for OpenDDS::DCPS::DataDurabilityCache:


Public Types
typedef DurabilityArray< DurabilityQueue< sample_data_type > * >	sample_list_type
typedef ACE_Hash_Map_With_Allocator< key_type, sample_list_type * >	sample_map_type
typedef std::list< long >	timer_id_list_type
Public Member Functions
	DataDurabilityCache (::DDS::DurabilityQosPolicyKind kind)
	Constructor.
	~DataDurabilityCache ()
	Destructor.
bool	insert (::DDS::DomainId_t domain_id, char const topic_name, char const type_name, DataSampleList &the_data,::DDS::DurabilityServiceQosPolicy const &qos)
bool	get_data (::DDS::DomainId_t domain_id, char const topic_name, char const type_name, DataWriterImpl data_writer, ACE_Allocator mb_allocator, ACE_Allocator *db_allocator,::DDS::LifespanQosPolicy const &)
Private Member Functions
	DataDurabilityCache (DataDurabilityCache const &)
DataDurabilityCache &	operator= (DataDurabilityCache const &)
Static Private Member Functions
static std::auto_ptr< ACE_Allocator >	make_allocator (::DDS::DurabilityQosPolicyKind kind)
Private Attributes
std::auto_ptr< ACE_Allocator > const	allocator_
	Allocator used to allocate memory for sample map and lists.
sample_map_type *	samples_
	Map of all data samples.
timer_id_list_type	cleanup_timer_ids_
	Timer ID list.
ACE_SYNCH_MUTEX	lock_
	Lock for synchronized access to the underlying map.
ACE_Reactor *	reactor_
	Reactor with which cleanup timers will be registered.
Classes
class	key_type
	Key type for underlying maps. More...
class	sample_data_type
	Sample list data type for all samples. More...

Detailed Description

Underlying data cache for both OpenDDS TRANSIENT and PERSISTENT DURABILITY implementations..

This class implements a cache that outlives DataWriters.

Member Typedef Documentation

typedef DurabilityArray< DurabilityQueue<sample_data_type> *> OpenDDS::DCPS::DataDurabilityCache::sample_list_type

typedef ACE_Hash_Map_With_Allocator<key_type, sample_list_type *> OpenDDS::DCPS::DataDurabilityCache::sample_map_type

typedef std::list<long> OpenDDS::DCPS::DataDurabilityCache::timer_id_list_type

Constructor & Destructor Documentation

OpenDDS::DCPS::DataDurabilityCache::DataDurabilityCache ( ::DDS::DurabilityQosPolicyKind kind )

Constructor.

OpenDDS::DCPS::DataDurabilityCache::~DataDurabilityCache ( )

Destructor.

OpenDDS::DCPS::DataDurabilityCache::DataDurabilityCache ( DataDurabilityCache const & ) [private]

Member Function Documentation

bool OpenDDS::DCPS::DataDurabilityCache::get_data	(	::DDS::DomainId_t	domain_id,
		char const *	topic_name,
		char const *	type_name,
		DataWriterImpl *	data_writer,
		ACE_Allocator *	mb_allocator,
		ACE_Allocator *	db_allocator,
		::DDS::LifespanQosPolicy const &
	)

Write cached data corresponding to given domain, topic and type to DataWriter.

Todo:: Is this going to cause problems for users that set a finite DDS::ResourceLimitsQosPolicy::max_instances value when OpenDDS supports that value?

Todo:: If we don't empty the queue, we'll end up with duplicate data since the data retrieved from the cache will be reinserted.

bool OpenDDS::DCPS::DataDurabilityCache::insert	(	::DDS::DomainId_t	domain_id,
		char const *	topic_name,
		char const *	type_name,
		DataSampleList &	the_data,
		::DDS::DurabilityServiceQosPolicy const &	qos
	)

Insert the samples corresponding to the given topic instance (uniquely identify by its domain, topic name and type name) into the data durability cache.

std::auto_ptr< ACE_Allocator > OpenDDS::DCPS::DataDurabilityCache::make_allocator ( ::DDS::DurabilityQosPolicyKind kind ) [static, private]