Home > Contents > Index >
Template Tags TOC   |    Alpha TOC   |    Tag Family TOC   |    Purpose TOC   |    Annotated TOC   |    Index 

 

ics:disablecache

Disables caching.

Syntax

Description

Forces the current evaluation to not be cached by ContentServer.

Parameters

recursive (optional)
Default value is true. The recursive attribute is used to enable/disable caching of the child pages of the page in which disable cache is set.

Error Numbers

There are no possible errno for this tag.

Example

The following example disables caching.

The recursive attribute is used to enable/disable caching of the child pages of the page in which disable cache is set.

For the purpose of next examples, let us assume that we have a hierarchy of pages that are called recursively. For e.g. Parent page -> Page a -> Page b -> Page c. When we set the recursive attribute to true in page b, all three pages a, b and c are NOT cached. In general, when we specify recursive = true in the disable cache tag, all child pages of that page are NOT cached, unless those pages have been previously called before setting the disable cache tag.

Note: In all of the following examples, we assume the page hierarchy a->b->c->d->e

Examples to illustrate different scenarios

In the above example, since recursive is set to true, none of the pages are cached.

In the above example, since page c was called before disable cache was set, Page c along with Page d and Page e WILL be cached, but the pages a, b will NOT be cached.

In the above example, pages c and d will be cached, whereas a, b and e will not be cached.

On the other hand when we WANT to cache child pages, we set recursive to be ‘false’. When we do so, we cache all the child pages that are called after this tag is set. For e.g.

Here we DO NOT cache the pages a, b, but we cache pages c and d. The basic idea is: use disable cache with recursive = true to STOP caching all child pages

On a different note, when used with satellite server, disable cache works differently as explained below.

With this example, assuming we are calling through Satellite Server, then the call to (e) is a new request, so it will get cached. Both c and e will be cached.

  Home > Contents > Index >

FatWire JSP Tag Reference
Copyright 2005 - 2011 by FatWire Corporation
All rights reserved.