| || |
html & url modes
can some one give me a couple of examples about where i can use html mode & url mode?
Re: html & url modes
Differences between HTML and URL modes
applies to web vusers only
... sometimes called context sensitive. Is indeed a context-sensitive mode: during recording process, the replies from server are stored in vugen's cache. The subsequent mouse click on link or image on page are causing for the functions like web_link() or web_image() to be generated.
Example of HTML recording session:
* we open <http://www.google.com/>
* the server (google) sends us the page
* vugen's proxy keeps the copy of the page in its cache (memory)
* the google's starting page appears in browser
* vugen generates web_url() function
* Next, we click on the link saying Google Search Appliance
* vugen asks its cache: "hey, cache, what is the url behind that link?"
* the cache answers: "it is: http://www.google.com/appliance/ "
* vugen says "aha! now I know!" and generates function web_link()
During replay of the script recorded in the above example:
* vugen shoots web_url() function to open the main page
* the reply comes back from Google. The copy of the main page is stored in the vugen's cache.
* next, there's web_link() function. vugen asks its cache "hey, buddy! Can you tell me the url behind the text in the link saying Google Search Appliance, please?"
* the cache answers "sure! here it goes: http://www.google.com/appliance/" and happy vugen sends GET request to Google asking for appiances' page
... sometimes called analog or HTTP mode, means that all the requests are recorded and no data is cached.
Why the hell do we need both?!
THE answer is: to make our life easier! How?
Well, in the example above, the script we get using the HTML mode is short and easy to read.
And here's is a conclusion from the above:
in case your pages contain link(s) and/or request(s) generated by
* Macromedia Flash
* Java Applet
* VB script
* any 3rd party plug-in
you, probably, should use the URL mode.
Another thing to remember: the mechanism of cache usage during HTML mode costs us both memory and CPU power. The difference in memory and CPU consumption (footprint) between HTML and URL modes is not extreme. And it should be considered in cases of a very big loadtests (probably, 1000+ VUs).
Please, note that both modes simulate the real browser's activity in equally right way.