-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: How does responses works? #9
Comments
You are right your approach should work
"response":"auth"
"response":"opponentFound" ...and 3rd sampler will respond to opponentFound. And thanks for sharing your problems, I will keep this in mind when developing the plugin further. |
Great, thank you for your (quite fast!) answer! |
Response doesnt work for me ( |
Have a look at the View Results Tree -> Sampler Result there should be a detaild breakdown of all actions and how long did it take for the response to arrive. |
response from the server come immediately, but sampler took all 5sec (or more, depends on response-timeout-section) Now i have one more strange behavior! If i have some samplers, and set in 1st response-pattern this:
and leave other blank (!), all samplers fired immediately as recived a response from server. Whats going on?) |
same behaviour when i leave first sampler blank |
Could be something to do with regular expression processing. Maybe escaping special characters with \ would help |
i have workflow: several queries one by one. Once i got responce from 1st query, i want fire next one.
So i try to play with "response" section and with no success (
so my 1st request:
and i got response:
so i expect, the pattern i looking for is "auth" - should works great, right?
what i should to do - place this pattern to 1st sampler, or 2nd, or maybe both?
and i going to answer him "ok, i take this opponent"
how? Should i create 3th sampler with big response-timeout and place "opponentFound" in response-section, and then create 4th sampler with answer-request, right?
The text was updated successfully, but these errors were encountered: