Might I suggest that JMeter must also retrieve parse the result and retrieve Framesets
automatically otherwise Timers will become increasingly unusable!
Take as an example a login.jsp URL that upon successful authentication returns the
following (Home) page:
<frameset rows=52,* framespacing=0 frameborder=no border=0>
<frame name="witopbar" src="topBar.htm" marginwidth=0 marginheight=0 scrolling=no
frameborder=0 NORESIZE>
<frameset cols=80,* framespacing=0 frameborder=no border=0>
<frame name="winavigationbar" src="navigationBar.jsp?WflowType=W" marginwidth=0
marginheight=0 scrolling=AUTO frameborder=0 target="rbottom" noresize >
<frame name="rbottom" src="welcomeDefault.jsp">
</frameset>
</frameset>
The browser interprets this and immediately sends THREE requests back to the server
a) toBar.htm
b) navigationBar.jsp
c) welcomeDefault.jsp
So I end up with several URLs sampled by the HTTP Proxy Server (not a problem in its
own right since this is an accurate picture of the load on the server)
My problem is that a Timer will place a delay between each of the three "sub" requests
when really it should not pause for these three at all!
The only options I see are to a) make the Timers more intelligent (by "grouping" them
into individual mouse-clicks) or b) make the HTTP Sampler behave more like a browser
and retrieve these frames automatically in a similar way to images.
What are your thoughts?
Paul Hearmon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
