GitLab

Introduction of the ConfigurableClientList::getCachedZoneWriter() method.

To ztable_segment_. The previous could be misunderstood, we have other
segments too.

Conflicts:
	ChangeLog
	src/lib/dhcp/subnet.cc
	src/lib/dhcp/subnet.h
	src/lib/dhcp/tests/subnet_unittest.cc

trivial, directly committing.

The test faked some internal state in an insufficient way.

So the memory client doesn't have to provide an interface to return it.
It was hairy to some extent.

Removing the release from the test, since the segment now destroys it
itself. We can't check all memory is deallocated at that moment in the
test (since we can't do it before the destroy -- it is not deallocated
fully yet, and can't do it after also, since the memory segment doesn't
exist). But that doesn't matter, since the segment checks by assert.

And not ZoneTableSegmentTest like before. Testing a mock class (and not
testing the real class) makes no sense.

Compiles, but tests don't pass. There's something rotten in there.

Conflicts:
	src/lib/datasrc/memory/memory_client.cc
	src/lib/datasrc/memory/memory_client.h
	src/lib/datasrc/memory/zone_table_segment_local.h
	src/lib/datasrc/tests/memory/memory_client_unittest.cc
	src/lib/datasrc/tests/memory/zone_table_segment_unittest.cc

Some people found the previous hard to follow.

Since it is not used for reloading a zone only. It is now ZONE_SUCCESS.

Conflicts:
	src/bin/auth/auth_srv.cc
	src/bin/auth/tests/auth_srv_unittest.cc