Module: check_mk
Branch: master
Commit: c66a942015572b64edef23933b45c5bba8cd0c32
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=c66a942015572b…
Author: Mathias Kettner <mk(a)mathias-kettner.de>
Date: Fri Oct 11 01:17:11 2013 +0200
Updated bug entries #0983
---
.bugs/983 | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/.bugs/983 b/.bugs/983
index 6e8d41d..b939259 100644
--- a/.bugs/983
+++ b/.bugs/983
@@ -15,3 +15,17 @@ with a cached result.
Also we should cache queries needed for the search filters that
are contained in many views. The caching could be done by
the livproxyd.
+
+The caching should take into account if the core has been
+changed its configuration. For example the list of check
+commands, host groups and stuff can only change due to
+a configuration reload. So we can safely cache such a query.
+
+Question is, how the proxy could know that it should cache.
+A new Cache: header? But then the proxy would need to parse
+the headers completely. Or we simply make a:
+if "\nCache:" in request:
+ ....
+
+Cache: 500 --> Sekunden
+Cache: reload --> Bis config reload