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

The test faked some internal state in an insufficient way.

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

They are the reload() tests reused for this purpose. They fail, since
the method is temporary and contains almost no code.

This'll allow us to reuse them for testing the ZoneWriter approach for
the same purpose as reload(). The ZoneWriter one is not there yet, so
this is an equivalent change functionality-wise.

the points of the test should be preserved, but some internal behaviors
have to be adjusted.

it compiles, but some tests currently fail.

using EXPECT_EQ(==) instead.

- add zone and file names to masterload errors
- catch masterload error and log it
- don't quit auth completely on a single zone load failure

We change the file, not the memory content.

We have a class to keep a reference to it. This is in C++ only yet, the
python part needs to be implemented.

It considers NULL to be int and gets confused when instantiating
templates of the GTEST library.

They are special-cased on loading and they need to be special-cased on
reloading too.

Tests and actual error handling of various scenarios when loading zone
data to caches.

Only the ones that are requested.

This needs a lot of error handling added.

But it is not yet filled up

It is not created now, but there's the place to put it.

And change the parameter type in configure, since we want to preserve
the exact instance and we don't want to do a (deep) copy.

Except in the database, which was changed to private.  It was not meant
to be public and hasn't actually been used except for tests and internally
in the database version.

The list.{h,cc} is too generic.

They are likely not to be useful anyway and this allows a small
optimisation.