GitLab

Instead of hard-coded enum type. The data source should be agnostic to
the type.

Saying the segments are for in-memory cache. Also adding note about
future extending and exceptions.

SEGMENT_MAPPED may be misleading in case of locally-allocated memory.
Using SEGMENT_INUSE.

Specify the segment type used. This is SEGMENT_LOCAL for now with every
segment used, but it is ready for when we have different kinds of
segments too.

* Don't base it on the type of segment (eg. remove MSS_LOCAL).
* Use a SEGMENT_ prefix instead of MSS_ (MSS reportedly usually refers
  to something else).

Make the segmentState property of the DataSourceStatus immutable, making
the whole class read-only (except for assignment, which is needed for
putting it into a vector).

So one can extract status of all the data source clients from the list
and allow using it from future management of the memory segments.

Just a thin state holder class

We now allow having data sources with the same name if they are in
different classes. It would be significantly harder to implement and we
can identify the sources by the class+name tuple.

Read the name of the data source client from configuration or guess it.
Throw in case it isn't unique.

Test the names of the data sources in client lists in the C++ code as
well as in the configuration checker.

Which isn't at the moment, so it fails.

An optional name of the client in the client list in data source. No
handling done yet, only added to the spec file so it can be set.

Conflicts:
	src/bin/cmdctl/tests/cmdctl_test.py

- set 'file used' to None if set to nonexistent file
- remove couple of unnecessary test value checks
- slightly more efficient temporary file write

The rpcCall method in C++

They save only little bit of work to the CPU and are suspicious to
casual reader, even when they should be safe in theory.

fix conflict in changelog

Some slight grammar changes.
Mostly in comments, but some for api docs.
Changes a isc_throw output too.

Reviewed via jabber.

because it is a message ID, add a changelog entry too.
(reviewed via jabber)

and use the holder in the unit tests as well