]> git.ipfire.org Git - thirdparty/knot-resolver.git/commit
projects / thirdparty / knot-resolver.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 35a281d) | patch
predict: refresh expiring records immediately
authorVladimír Čunát <vladimir.cunat@nic.cz>
Thu, 27 Jul 2017 09:25:59 +0000 (11:25 +0200)
committerVladimír Čunát <vladimir.cunat@nic.cz>
Thu, 27 Jul 2017 11:49:32 +0000 (13:49 +0200)
commit965bab926f673ba0970834497b3bebfacd0201e5
tree10c64332fa42c3732fd59804e4459954ff1dc307tree
parent35a281d1a86d296a818449c9963be233db8bba27commit | diff
predict: refresh expiring records immediately

It seemed a bit strange to have 'stats' module collect expiring records
in an LRU, then once a few minutes convert that via JSON to a lua table,
and put those records into prefetching queue.  Apart from complexity,
it wouldn't work well with short TTLs typical for today's CDNs, e.g. 30
or 60 seconds.
modules/predict/README.rst diff | blob | blame | history
modules/predict/predict.lua diff | blob | blame | history
Mirror of https://gitlab.nic.cz/knot/knot-resolver.git