Ajax View application was designed to improve developer's visibility into and control over their web applications' behaviors on end-user's desktops.

The Ajax View approach is to insert a server-side proxy (or web server plugin) in-between the web server machines and the end-user's browser. This proxy captures the web application's JavaScript code as it is being sent to a browser and rewrites the code to insert extra instrumentation code.

The injected instrumentation code runs with the rest of the web application inside the end-user's browser and can capture performance, call graph, application state and user interaction information, providing visibility directly into the last hop of the user's experience.

Use the Ajax View proxy to gather performance profile information for a web application, without modifying the original web application, and without installing any extra plugins, ActiveX controls or extensions in the web browser.

Here are some key features of "Ajax View":

· Serve different instrumentation code to different users. This allows us to distribute instrumentation code across many users, spreading the cost of gathering lots of information such that no single user pays a high performance penalty.
· Adapt an instrumentation policy and serve different instrumentation code over time. For example, we can drill-down into performance problems and gather extra context about bugs


Ajax View works by using a proxy to intercept and rewrite the JavaScript code of a web application and automatically inject instrumentation code. The rewriting is controlled by one or more instrumentation policies, embedded within the proxy

The Ajax View JavaScript Instrumentation Proxy is an HTTP proxy that dynamically instruments JavaScript applications to monitor their performance and behavior within a Web browser. The Ajax View proxy's instrumentation can be extended through plug-ins. A sample plug-in is provided.

Requirements:

· NET Framework 2.0