Package org.frontcache.io
package org.frontcache.io
-
ClassDescriptionThe config files the management API will write, and the only names
set-configaccepts.Reads, hashes, backs up and atomically replaces a config file under FRONTCACHE_HOME/conf.Dry-parses a candidate config file beforeset-configwrites it.Whatset-configactually does, with no HttpServletRequest in sight.Bot classification config from ./conf/bots.conf: the ordered rules, and the bare User-Agent keywords.The raw ./conf/bots.conf of one node, for the console's Bot Configs screen.URL patterns that are never cached, from ./conf/dynamic-urls.conf.The raw ./conf/dynamic-urls.conf of one node, for the console's Dynamic URLs screen.URL-pattern to fallback-file mappings from ./conf/fallbacks.conf.The raw ./conf/fallbacks.conf of one node, for the console's Fallback Config screen.Response for the get-guard-rules action: the guard rules this node is running, in evaluation order (built-ins first, then conf/guard-rules.conf), each with its hit count since start.get-plugin-config: a plugin'sconf/<config>as it is on disk (or on the class path), comments and blank lines kept - what the console's Plugin Configs screen shows and edits.Raw content of ./conf/resilience.properties (comments and empty lines preserved), for display in the console.The cheap, pollable view of a node: cache sizes and the JVM they live in.One plugin asget-node-statsreports it: what it is (from its manifest), its state, and its counters.Response for theput-to-cacheIO action.The outcome ofreload-dynamic-urls: how many patterns are now active.reload-plugin-config: what re-reading a plugin'sconf/<config>did.The outcome ofreload-resilience.Whatset-configdid, or refused to do.