Hi,
>My only complaint at this time is
> that in HttpSamplerFull, your timing data includes the time it took the
> jmeter client code to parse the HTML and extract the links. I think it would
> be best to only time the connections to the server. Although the total user
> experience would depend on how fast their browser parses the html, it's
> debatable whether client processing is part of 'server performance" testing.
> In any case, users would have legitimate questions about just exactly what
> JMeter is testing, and I think it would be easiest for all involved if the
> answer was simply the server's time to finish responding to request.
>
> -Mike
Mike, You read my mind exactly.
I've modified HTTPSamplerFull.java to take into consideration your comments. In
addition, for all images, applets which are downloaded together with the main url,
I've kept a separate SampleResult for each of them. This way, the HTTP response code
and donwload time for each of them can be kept as well. The SampleResult for all
these are stored in the Map of the main SampleResult as an ArrayList. I'm in the
process of writing a new View Results Visualizer which is a jTree that shows the
relationship between all these SampleResults. Will post it here once I'm done.
I'm also considering creating a new GraphVisualizer
which displays the load times of the components of the html page (images, applets etc)
as well as the total load time. Please express view on this and suggestions.
Thanks.
--
__________________________________________________
Get FREE 50 MB email @ http://www.AtoZasia.com
Powered by Outblaze
HTTPSamplerFull.java
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
