summaryrefslogtreecommitdiffstats
path: root/lib/base/namespace.hpp
blob: 94f2055d373291f60806676f2c859ec857528871 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
/* Icinga 2 | (c) 2012 Icinga GmbH | GPLv2+ */

#ifndef NAMESPACE_H
#define NAMESPACE_H

#include "base/i2-base.hpp"
#include "base/object.hpp"
#include "base/shared-object.hpp"
#include "base/value.hpp"
#include "base/debuginfo.hpp"
#include <atomic>
#include <map>
#include <vector>
#include <memory>
#include <shared_mutex>

namespace icinga
{

struct NamespaceValue
{
	Value Val;
	bool Const;
};


/**
 * A namespace.
 *
 * ## External Locking
 *
 * Synchronization is handled internally, so almost all functions are safe for concurrent use without external locking.
 * The only exception to this are functions returning an iterator. To use these, the caller has to acquire an ObjectLock
 * on the namespace. The iterators only remain valid for as long as that ObjectLock is held. Note that this also
 * includes range-based for loops.
 *
 * If consistency across multiple operations is required, an ObjectLock must also be acquired to prevent concurrent
 * modifications.
 *
 * ## Internal Locking
 *
 * Two mutex objects are involved in locking a namespace: the recursive mutex inherited from the Object class that is
 * acquired and released using the ObjectLock class and the m_DataMutex shared mutex contained directly in the
 * Namespace class. The ObjectLock is used to synchronize multiple write operations against each other. The shared mutex
 * is only used to ensure the consistency of the m_Data data structure.
 *
 * Read operations must acquire a shared lock on m_DataMutex. This prevents concurrent writes to that data structure
 * but still allows concurrent reads.
 *
 * Write operations must first obtain an ObjectLock and then a shared lock on m_DataMutex. This order is important for
 * preventing deadlocks. The ObjectLock prevents concurrent write operations while the shared lock prevents concurrent
 * read operations.
 *
 * External read access to iterators is synchronized by the caller holding an ObjectLock. This ensures no concurrent
 * write operations as these require the ObjectLock but still allows concurrent reads as m_DataMutex is not locked.
 *
 * @ingroup base
 */
class Namespace final : public Object
{
public:
	DECLARE_OBJECT(Namespace);

	typedef std::map<String, NamespaceValue>::iterator Iterator;

	typedef std::map<String, NamespaceValue>::value_type Pair;

	explicit Namespace(bool constValues = false);

	Value Get(const String& field) const;
	bool Get(const String& field, Value *value) const;
	void Set(const String& field, const Value& value, bool isConst = false, const DebugInfo& debugInfo = DebugInfo());
	bool Contains(const String& field) const;
	void Remove(const String& field);
	void Freeze();

	Iterator Begin();
	Iterator End();

	size_t GetLength() const;

	Value GetFieldByName(const String& field, bool sandboxed, const DebugInfo& debugInfo) const override;
	void SetFieldByName(const String& field, const Value& value, bool overrideFrozen, const DebugInfo& debugInfo) override;
	bool HasOwnField(const String& field) const override;
	bool GetOwnField(const String& field, Value *result) const override;

	static Object::Ptr GetPrototype();

private:
	std::shared_lock<std::shared_timed_mutex> ReadLockUnlessFrozen() const;

	std::map<String, NamespaceValue> m_Data;
	mutable std::shared_timed_mutex m_DataMutex;
	bool m_ConstValues;
	std::atomic<bool> m_Frozen;
};

Namespace::Iterator begin(const Namespace::Ptr& x);
Namespace::Iterator end(const Namespace::Ptr& x);

}

extern template class std::map<icinga::String, std::shared_ptr<icinga::NamespaceValue> >;

#endif /* NAMESPACE_H */