HTTP caching is maintained without the knowledge of any technique that is provided with the platform on which the Siebel gets installed. The services are made to transparent to ALLOW the caching to be dynamic and there is a caching that takes place for both dynamic and static content. The dynamic content caching is saved as long as the program runs and the static content are saved till the user removes the cache from the BROWSER.

The examples of Image file can be taken in this case that allow the static content to be cached by using NetScaler. The dynamic generation of the APPLICATION content allow it not be cache-able as it allows more space and logic to STORE the dynamic content. The caching can be adjusted by changing the maximum size and header string and other changes can be done by going to the settings area.

HTTP caching is maintained without the knowledge of any technique that is provided with the platform on which the Siebel gets installed. The services are made to transparent to allow the caching to be dynamic and there is a caching that takes place for both dynamic and static content. The dynamic content caching is saved as long as the program runs and the static content are saved till the user removes the cache from the browser.

The examples of Image file can be taken in this case that allow the static content to be cached by using NetScaler. The dynamic generation of the application content allow it not be cache-able as it allows more space and logic to store the dynamic content. The caching can be adjusted by changing the maximum size and header string and other changes can be done by going to the settings area.