Mike, Ok, I'm cleaning it up so I can send it to you.
About the other modifier, yes, that is helpful. Thanks! --Dave 2002/01/24 23:51:21, "Stover, Michael" <[EMAIL PROTECTED]> wrote: >First of all, yes it would be useful to others. > >If I understand right, then I think you can already do what you want - which >is to set up x threads, each with it's own unique value for a parameter that >gets set once and only once. Is that right? > >So, simplest solution, if you want to login each thread as a different user, >put the Modification Manager with it's Web Test and modifier under a Once >Only Controller. This way, each thread will get a unique value, the thread >will be logged in, and then it will never run again. > >If you want a more universal solution, then I'd suggest creating a mapping >between the thread name and it's assigned unique value. Every thread gets a >unique name, and you can ask at any time what the current thread's name is. >Thus, in your modifier, you can keep this information in a hashmap. If the >thread has a value already, simply retrieve it from the hashmap using the >thread's name. If it doesn't, then create the unique value, and store it >appropriately. > >Will that work for you? > >-Mike > >> -----Original Message----- >> From: David La France [mailto:[EMAIL PROTECTED]] >> Sent: Thursday, January 24, 2002 1:51 AM >> To: jmeter-dev >> Subject: modifiers >> >> >> Hi, >> >> I have a couple of questions. >> >> I'm trying to figure out how to implement a http parameter >> modifier so that every thread in a threadgroup would get a >> unique value for that parameter..for example, if >> one parameter to a servlet is a user id, then ideally you >> would like every thread in the group to have a unique user >> id, so that each thread appears to the servlet as a >> unique user. >> >> I already created a http parameter modifier that allows a >> thread to change a parameter, so that every time through that >> thread's loop, the parameter has a different >> value. >> >> However, I am having a hard time figuring out how to >> implement the former. >> >> If I use a static object to dole out the values, then threads >> that are not even in the same threadgroup will ALSO get their >> values from this object...which would >> obviously be a Bad Thing. >> >> Is there some way I can attach this object to the thread >> group itself, so that only its threads could access it? >> Should I give up and do it the other way? >> >> My other question is: would the http parameter modifier that >> I already implemented be useful to anyone else? Should I >> look into submitting it to the project? >> >> Thanks for your time! >> David La France >> >> >> >> -- >> To unsubscribe, e-mail: >> <mailto:[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]> > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
