Howdy Robert, I'm pretty new at the BDL recording and scripting but from my experience, the measurements are based on the request timer that is coded for the AJAX call. If you are not controlling the sync timer, then the time is how ever long the browser context takes to return to idle state. So, if you using a basic AJAX call then it is included since the browser context will return to idle when the AJAX has sent the response complete. If you are using AJAX in a polling fashion, only the time that the first AJAX poll is included since after the first AJAX poll, the browser context would return to idle state. If you are using AJAX in a long run reverse proxy (Comet style) then the entire AJAX interaction is included. In the case of long running AJAX (Comet style - reverse proxy) then you can injected Sync Timers BrowserSetOption(BROWSER_OPT_SYNC_TIMEOUT, 3000); This would limit the time that the Browser will wait for the idle state of the AJAX call. You could show this by injecting Measure Timers: MeasureStart("TMainTimer1"); ... WebPageSubmit ... WebPageAddUrl ...WebParseDataBoundEx MeasureStop("TMainTimer1"); Then you can narrow the Measure Timers then show within the TrueLog the start of the timer, what is included in the timer and when the timer is stopped. Would like to thank Danny from Microfocus SilkPerformer support for the large amount of help to understand how this works. Billy
↧