After the recording, a User Path using AMF polling is displayed as follows.
Once processed by the NeoLoad Post-recording wizard, the User Path is modified as follows.
NeoLoad has made the following noticeable changes:
POLLfor example). This request has been placed in a loop (
polling_whilefor example), which continues to loop until the
NL-stopPollingvariable generated by NeoLoad becomes
true. Lastly, the loop itself has been placed in a secondary execution thread using a fork action (
push_forkfor example). For more information, see Polling requests.
NL-stopPollingvariable, with the
falsevalue, to have the polling function work on every Virtual User iteration.
polling_delayis the average of the time intervals between two polling requests in the original User Path.
stop_pollingvariable modifier triggers the exit from the polling loop by modifying the value of the