Engine for Web Applications ConfigurationFile Size: 31870 bytes
Last Modified: 2/29/2008 10:28:40 PM
Content Created: April 2006
Summary:
This document describes the XML configuration formats used in Engine for Web Applications.
Engine for Web Applications OverviewFile Size: 27541 bytes
Last Modified: 2/29/2008 10:28:40 PM
Content Created: May 2003
Summary:
JavaScript Function Monitor 2.1File Size: 19605 bytes
Last Modified: 4/29/2008 11:52:31 PM
Summary:
JavaScript Function Monitor 2.1 is a script-based debugging tool.
It is very useful for identifying performance problems from within the browser.
Works in Internet Explorer and Netscape Navigater 4.x and above, and in Mozilla-based browsers.
Function Monitor integrates with JavaScript Profiler for ease of metric collection.
JavaScript Profiler 2.0File Size: 20714 bytes
Last Modified: 5/6/2008 6:50:05 PM
Summary:
JavaScript Profiler 2.0 is a context-menu extension for Internet Explorer 6 and later.
It identifies JavaScript functions by internal script blocks and external files, object model inspection, and accesses the live DOM via the Active Source utility.
For monitoring JavaScript performance across browsers, refer to the Function Monitor project.
Optionally, Active Source is available as a separate context-menu extension.
Multi-Document Interface Script APIFile Size: 37999 bytes
Last Modified: 4/27/2008 1:31:58 PM
Summary:
The Multi-Document Interface (MDI) Script API is an object-oriented DHTML Window toolkit.
It includes a common approach to skinnable UIs in DHTML, off-screen buffering of content using XML,
a few example widgets such as a rich buffered select control, and a scalable design that allows new components to be inserted into the architecture.
At present, browser support is limited to Internet Explorer 5.5 and above, Netscape 6.2, and Mozilla 0.9.3. Bugs in Mozilla in more recent versions, up through 0.9.8, cause browser crashes.
Development of the MDI API is halted. Refer to the Engine for Web Applications project for related work.
Web Page Passive MonitoringFile Size: 30817 bytes
Last Modified: 2/29/2008 10:28:41 PM
Summary:
This article describes how to build client-side passive monitors using Engine for Web Applications.
Passive monitoring is the practice of recording metrics in response to outside stimuli. Conversely, active monitoring is the practice of generating stimuli and then recording the resulting metrics. Both active and passive Web site monitoring can take place at any point where the network traffic, application transactions, or user events generate data.