I think the approach I would prefer to take is the invention of another controller - the "Transaction Controller", perhaps, that would group requests and control the delivery of their sample results. Or, maybe even easier, not control their sample results, but simply add an extra one that encompasses the whole bunch. The problem I had for doing this is that I don't see a simple way of making this an accurate timing the way the samplers do. The transaction time would include all sorts of JMeter processing that you might not want. Timers would get included. All of it. So, I question the value of such a thing.
Another option is to make a smart visualizer that let's you control how timing information is grouped. If you tell it "group requests x,y,and z and combine their data to look like a single request", that might get you what you want. You would have to write a new visualizer, and you'd have to know something about how to gather information from JMeter's test tree - not hard, but not well documented. -Mike > That was not such a dumb question after all! I thought I was missing > something in the docs. > Would not it be possible to put requests within requests and tie > listeners to the aggregated sample at each level ? > Something like a Composite pattern on requests ... > By the way, I could possibly manage to contribute some time to this > topic if you could give me hints about where > to look at. I've just begun delving into JMeter to incorporate it into > an applet and I am quite confused by the structure of the project. > > Arnaud > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- Michael Stover [EMAIL PROTECTED] Yahoo IM: mstover_ya ICQ: 152975688 AIM: mstover777 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
