The goal of the Ajax View project is 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.
Because Ajax View is rewriting web application code dynamically each time a user visits the web site, it can:
- 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
Notes
- Using Ajax View does not require modification of either the page source or the browser.
- You can customize Ajax View to monitor exactly the JavaScript behavior you're looking for, whether it's about performance, or how people navigate through your site.
Getting Started with AJAX View