Browser Web Cache Web App Server Database 1. Client sends Http request 2. Web Cache responds immediately if cached object is available 3. If object is not in cache, Web Cache requests object from Application Serv 4. Application Server generates response(may include Database queries) 5. Application Server responds to Web Cache 6. If response is cacheable, Web Cache retains a copy for subsequent requests 7. Web Cache compresses page and responds to Client Figure 2: How Web Cache works "With OracleAs Web Cache serving In addition to intelligent consistency management, an effective dynamic caching up dynamic content solution must address content disambiguation, session management and personalization. Disambiguating content is essential for properly storing and enough that Specialized can delivering documents and maintaining high cache hit rates. URLS, normally th unique identifiers for static content caches, are often insufficient for dynamic increased bandwidth and serve horsepower at the back end And content due to request-specific content generated by applications. For example,a less processing- not just on the browser-aware application may generate different responses for different browsers database servers, but also by Web for the same URI server applications- means the Likewise, Web-based applications often need to maintain session state(such as customer has more time to get out shopping carts)for every user. Some applications embed the session state within pecialized experience is all about. the URL and hyperlinks as an alternative to cookies. A naive cache would interrupt Ron Pollard, cIO, Specialized Additionally, pages with embedded session state become unique for each session Bicycle Components, Inc. Unlike traditional static caches, OracleAs Web Cache supports a number of dvanced caching policies for dynamically generated content, such as caching multiple-version documents for the same URL, and session-aware rules for pages containing session informatior OracleAS Web Cache 10g(10.1.2)-Technical White Pap right 0 1999-2005 Oracle Corporation, All Rights ReservedPage 10 OracleAS Web Cache 10g (10.1.2) -- Technical White Paper Copyright © 1999-2005 Oracle Corporation, All Rights Reserved Figure 2: How Web Cache works. In addition to intelligent consistency management, an effective dynamic caching solution must address content disambiguation, session management and personalization. Disambiguating content is essential for properly storing and delivering documents and maintaining high cache hit rates. URLs, normally the unique identifiers for static content caches, are often insufficient for dynamic content due to request-specific content generated by applications. For example, a browser-aware application may generate different responses for different browsers for the same URL. Likewise, Web-based applications often need to maintain session state (such as shopping carts) for every user. Some applications embed the session state within the URL and hyperlinks as an alternative to cookies. A naïve cache would interrupt the session establishment during cache hits and prevent new session creation. Additionally, pages with embedded session state become unique for each session and defeat simple caches. Unlike traditional static caches, OracleAS Web Cache supports a number of advanced caching policies for dynamically generated content, such as caching multiple-version documents for the same URL, and session-aware rules for pages containing session information. “With OracleAS Web Cache serving up dynamic content, the performance increase is great enough that Specialized can significantly reduce the need for increased bandwidth and server horsepower at the back end. And less processing – not just on the database servers, but also by Web server applications – means the customer has more time to get out and ride, which is what the Specialized experience is all about.” Ron Pollard, CIO, Specialized Bicycle Components, Inc