How is OracleAS Web Cache able to cache dynamically generated pages?
Caching dynamically generated content is not easy, especially for traditional caching products originally designed to store static content. Products and services that cache static content are typically unable to serve dynamic content because they lack the means to manage the consistency of Web pages vis-à-vis the data sources used to create them. Naive caching products also force customers to rely on expensive and complex content propagation tools to update their caches with new content. Furthermore, these content propagation tools cannot handle the volume and frequency of content updates demanded by today’s Web application architectures. In contrast, OracleAS Web Cache was built from the ground up to cache volatile Web content. OracleAS Web Cache employs advanced invalidation mechanisms to maintain consistency with origin data sources, such as file systems, content management tools, databases and content feeds. Using a combination of administrative commands, database triggers and prog
