GitLab

this should fix the timeout problem

Also moved initialization of the cache to Resolver

they appeared to still have been too low for some systems

Though most of the tests fell into recursive_query_unittest.cc

and updated some doxygens as per Jeremy's mail

client timeout and auth errors now result in SERVFAIL being sent back
added copySection and moved copyAnswerMessage to resolve.cc (no need to
have that in asiolink)

In particular:
* Use Use asiolink abstractions instead of Boost::asio directly
* Add cross-section checks (answer/question v authority)
* Extended description of bailiwick
* Methods added to isc::dns::Message and asiolink::IOAddress

Removed some dead code, added two unit tests, changed sendQuery() to the
more descriptive resolve(), and removed a superfluous call to dlog()

It tried to bind to 255.255.0.0, which should fail, but doesn't on some
systems (CentOS for example). As a possible way forward, I've changed it
to 192.0.2.0, which does fail on CentOS. If this does not fail on other
systems, we should probably go for the proposed solution from #437, or
remove the test completely.

The tests worked, but the timeouts were so small that on somewhat slower
systems the tests could fail. Increased them a bit.

for now. We'll need to come up with a structural way to test those

Modified the interface of IntervalTimer to accept interval in
milliseconds.
Tests for IntervalTimer are also modified; now it takes 1.4 seconds.

Renamed IntervalTimer::setupTimer() -> IntervalTimer::setup()
Renamed IntervalTimerImpl::updateTimer() -> IntervalTimerImpl::update()

Removed some unused debug code and cleaned up some white space.

mostly whitespace, one comment update and two lines of dead code

briefly talked about it on jabber, no one opposed to it, Jeremy explicitly
agreed.  changes are trivial themselves, so no explicit review.

Note that client_timeout at this point has the same result as
lookup_timeout.

Changed self-deletion of RunningQuery a bit, as it
cannot delete itselfs until we are sure there are not events coming in
anymore. If we change the clientTimeout() callback to send an answer and
not stop, we shall need to keep track of that fact (i.e. not send back
an answer in the end, and update stop since it won't be called by
clientTimeout() anymore

When adding the asiolink tests for these features, added a few
convenience functions for common code in those tests.

removed some debug statements, updated some dlog() calls
Added two tests for resolver. Right now, these tests make it resolve
addresses in the public dns (www.isc.org and an nxdomain in isc.org),
we'll need to do something better in the long run, but for now i just
want to able to test resolving

the timer.

other tests.