Most server-side .NET, ActiveX, and Java components are typically used on just a few web pages throughout a site. One example of this is a component that sends an email message when someone submits a form. Another example is a component that allows a file upload through their browser. In these typical scenarios, the components are used infrequently relative to the number of pages viewed by a visitor on your site.
BrowserHawk usage, on the other hand, tends to be different in that many developers need information from BrowserHawk about the visitor's browser and system capabilities on the majority, if not all, of their pages.
BrowserHawk therefore is built from the group up to provide enterprise-class scalability and performance, even when it is used under heavy load on the majority, or all, of your pages.
To achieve this high level of performance, BrowserHawk provides two levels of built-in caching that operate together. These are "DashCache™" and "Automatic Session Caching", and are discussed in detail in the following two sections.
See Also: