As we want to directly modify the ZoneTable in ZoneReloaderLocal
(because it is memory-type dependant), we don't need the InstallAction
for anything. If we don't need it, we don't pass it as constructor
parameter -- it'll be called from a factory anyway and the factory may
know we don't need it.

Also adding a setTable() method to ZoneTableHeader. The header had no
way to specify the table currently and we need it for the tests. The
method is currently tentative, we'll probably replace it by something.

NULL makes no sense, so throw in that case.

We allocate the ZoneData in the LoadAction, to match what happens in
ticket #2268 -- there's a function to load zone which allocates it
itself, we want to use it.

This might be less confusing.

Someone O:-) forgot to add it in the ^^ commit.

The interface was slightly updated, to suit the needs (added some more
parameters). Some of it might be wrong, but I'm not sure about it.

Doesn't compile, there's no (not even empty) implementation of many
methods of the updater.

Planned for merge #2268

And make it slightly stronger (it now checks something that should be
mostly obvious too, but who knows, with software).

Instead of releasing it directly. While the internal release was more
convenient, it didn't allow for swapping things fast under a mutex and
then spending the time releasing it unlocked.

It is supposed to be mostly private. Use it internally only.

this will prevent surprising test failure on an incrementally updated dev
tree.  okayed on jabber.

* The unique constraint on NSEC3 owner per zone is now removed
* NSEC3 RRSIGs are now returned next to their RR set
* Test was adjusted to check for RRSIGs too

They don't need the mutable versions to work, but they used them anyway.

This one was not mutable, it just took Name as an argument.

As the method was removed.

The domain tree no longer supports the mutable find versions, so we
don't need the template parameters allowing for them.

They are currently used in test code only (so we'll need to update the
tests to compile). The real code seams clean now.

Currently, the content of zone is passed to the addZone method. No way
to change it later, but the addZone overwrites the old value if called
again.

This should hopefully allow for removal of mutable find methods from the
tree.