These are essentially right. The Simple Controller doesn't do anything, but can be used as an organizational tool.
The Modification manager allows one to parse the results of previous requests, and use them to dynamically modify the next request. An example usage is illustrated in the current documentation. -Mike > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Saturday, November 10, 2001 10:26 AM > To: [EMAIL PROTECTED] > Subject: Re: Q: Simple examples of how to use the four Logic > Controllers? > > > Hi, > > Here's what I understand of the Logic Controller but only Mike can > give a definitive answer. Mike, can you confirm these? Thanks. > > - Interleave Controller > Samples only 1 'HTTP Request' instead of all 'HTTP Request's in > the 'ThreadGroup' for each iteration. > e.g. > - Simple Controller > I don't really know what this is used for b'cos the 'ThreadGroup' > itself is a 'Loop Controller'. Whether you put the 'HTTP Request' > under the 'ThreadGroup' or a 'Simple Controller' (which is under > the 'ThreadGroup' itself), there doesn't seem to be a difference. > - Loop Controller > The 'ThreadGroup' itself is a 'Loop Controller'. If you make > the 'ThreadGroup' iterate 2 times and you have a 'Loop Controller' > with a 'HTTP Request' looping 3 times under it, you'll get 6 samples. > - Once-Only Controller > Whatever 'HTTP Request' under this controller will only be executed > only once EVEN if the 'ThreadGroup' is made to iterate more than once. > - Modification Manager > Don't know what this is. > > Hope this helps. > > neth > > ---- Begin Original Message ---- > > From: "Kevin Hammond" <[EMAIL PROTECTED]> > Sent: Fri, 9 Nov 2001 11:51:59 -0800 > To: <[EMAIL PROTECTED]> > Subject: Q: Simple examples of how to use the four Logic Controllers? > > > Hi, > > Would someone show me some simple and useful examples of how to use > each of > the four Logic Controllers? �I need them for the documentation I am > writing. > > Here is the existing documentation on Logic Controllers, but it is too > generic. > > --- > A logical controller is a controller that regulates the iterative > behavior > of it's sub-controllers, and sometimes, it can also affect the > behavior of > its parent controller indirectly. A logical controller can also > modify test > samples that pass through it. The essential distinction between a > logical > controller and a generative controller is that logical controllers > create no > test samples by themselves. If you add a logical controller to the > test tree > with no sub-conrollers, then it can have no effect on the test. It's > only > useful as a parent of other sample generating controllers. > --- > > Thanks! > Kevin Hammond > > > -- > To unsubscribe, e-mail: � <mailto:jmeter-dev- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:jmeter-dev- > [EMAIL PROTECTED]> > > > > ---- End Original Message ---- > > > > ______________________________________________________________ > For the latest news, go to http://www.asia1.com > > -- > To unsubscribe, e-mail: > <mailto:jmeter-dev-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
