It's been around for a while - I would say it's probably time to start using the HttpSampler2 in production settings.
If you don't use a listener that stores the response, the response will be discarded pretty quick. JMeter does not do IP spoofing. -Mike On Wed, 2005-07-27 at 18:12 +0200, Sergei Riaguzov wrote: > I'm sorry for the previous message. Something has screwed in my > head and the border between languages dissapeared. :) > > I have some questions about the HttpSampler2. > > 1. What is his status? He uses HttpClient and is very fast but > do you reccomend its usage in production environment? What should > be done to make it stable? What does it lack? > > 2. Is there any way except changing the source to specify that if > not needed HttpSampler2 should not download all the ResponseBody > to to somewhere and keep it for some long time? It's been noticed > that when there are many threads working concurrently there may > become a problem with big web pages.. Is there a way to get only > response size and other information and to discard response body > immediatly? Or even better - not to download it in HttpClient to > the memory but use some cycle buffor? > > 3. Is there an easy way to specify the IP addres for each sample? > For many samples? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
