A cache is a temporary store for documents that allows them to be quickly retrieved and served repeatedly – The purpose is to prevent a situation where repeated requests for a web address URI causes the server to duplicate effort fetching and reassembling data from various sources.
MKDoc has an internal cacheing mechanism at the document level. Authors can state how long they intend information in a document to stay current – This method is now deprecated in favour of a site-wide policy for cacheing all data, not just documents.
Cache Policies
As an example, a cache policy might say that articles are unlikely to change rapidly and can therefore be cached for a long time, however a news headlines page may change all the time and needs as little cacheing as is practical.
The policy for an MKDoc site can be tweaked to suit any such situation, but a basic policy will suffice for all but the most high-traffic situations. The policy is defined in a MKDoc::Control_List file like this: