Karel Slaný authored 8 years ago and Ondřej Surý committed 8 years ago

The control structure is part of the resolver context.

Karel Slaný authored 8 years ago and Ondřej Surý committed 8 years ago

Use ENABLE_cookies=yes variable to compile functionality.

Karel Slaný authored 8 years ago and Ondřej Surý committed 8 years ago

Cookies are not stored in separate cache.

Karel Slaný authored 8 years ago and Ondřej Surý committed 8 years ago

The cookies layer injects a new query into the plan when a DADCOOKIE
response is detected. After failing the second attempt a TCP fallback is
signalised.

iterator already checks this and also chain length,
however these checks were omitted in the rrcache
CNAME unroll loop

in normal mode, only final CNAME target is refetched, but
not intermediate CNAMEs. intermediate CNAMEs are *never* cached,
but they are used to get final name for requery. in strict mode now,
every CNAME target is explicitly fetched even if it's a chained CNAME.

forks are connected with IPC pipes to process
group leader and can execute expressions on its
behalf. so running commands over all workers
is easy now:

> hostname() -- single
localhost

> map 'hostname()' -- all
localhost
localhost
localhost

* SOA MINTTL always preferred for negative answers
* only SOA used for negative answers

refs #75

this is required to avoid REFUSED loops if the origin doesn't handle
minimisation well

this change introduces new API for cache backends,
that is a subset of knot_db_api_t from libknot
with several cache-specific operations

major changes are:
* merged 'cachectl' module into 'cache' as it is
  99% default-on and it simplifies things
* not transaction oriented, transactions may be
  reused and cached for higher performance
* scatter/gather API, this is important for
  latency and performance of non-local backends
  like Redis
* faster and reliable cache clearing
* cache-specific operations (prefix scan, ...) in
  the API not hacked in
* simpler code for both backends and caller