Classes |
struct | Offer_Map_Entry |
Public Types |
typedef
TAO_Service_Offer_Iterator
< LOCK_TYPE > | offer_iterator |
typedef
ACE_Hash_Map_Manager_Ex
< CORBA::String_var,
Offer_Map_Entry *, ACE_Hash
< CORBA::String_var >
, ACE_Equal_To
< CORBA::String_var >
, ACE_Null_Mutex > | Offer_Database |
Public Member Functions |
| TAO_Offer_Database (void) |
| No arg constructor.
|
| ~TAO_Offer_Database (void) |
CosTrading::OfferId | insert_offer (const char *type, CosTrading::Offer *offer) |
int | remove_offer (const CosTrading::OfferId offer_id) |
CosTrading::Offer * | lookup_offer (const CosTrading::OfferId offer_id) |
CosTrading::Offer * | lookup_offer (const CosTrading::OfferId offer_id, char *&type_name) |
TAO_Offer_Id_Iterator * | retrieve_all_offer_ids (void) |
Private Member Functions |
CosTrading::Offer * | lookup_offer (const char *type, CORBA::ULong id) |
int | remove_offer (const char *type, CORBA::ULong id) |
void | operator= (const TAO_Offer_Database< LOCK_TYPE > &) |
| TAO_Offer_Database (const TAO_Offer_Database< LOCK_TYPE > &) |
Static Private Member Functions |
static CosTrading::OfferId | generate_offer_id (const char *type_name, CORBA::ULong id) |
static void | parse_offer_id (const CosTrading::OfferId offer_id, char *&service_type, CORBA::ULong &id) |
Private Attributes |
LOCK_TYPE | db_lock_ |
Offer_Database | offer_db_ |
Friends |
class | TAO_Service_Offer_Iterator< LOCK_TYPE > |
template<class LOCK_TYPE>
class TAO_Offer_Database< LOCK_TYPE >
The TAO_Offer_Database encapsulates the mapping of service types to those offers exported with that service types. The underlying structure is a map of maps. The first maps maps the service type name to a map of exported offers. The second map maps the identifying index for that offer within the service types. So a service type name and an index uniquely identifies an exported offer. In fact, when the register export interface returns a CosTrading::OfferId, it's returning no more than a simple string concatenation of these two values. In addition to all these wonderful things, the TAO_Offer_Database has built-in locking, one reader/writer-style lock for modifying the top-level map and a reader/writer-style for each of the offer maps. Needless to say the locks are acquired when the TAO_Offer_Database performs operations on the structures they guard. NOTE: TAO_Offer_Database needs to be parameterized by a READER/WRITER LOCK, a RECURSIVE MUTEX, or a NULL MUTEX, not a simple binary mutex! Mutexes will cause deadlock when you try to contruct an iterator (which acquires a read lock on the map under an existing read lock). Just don't do it, ok?