After the recording, a User Path using the WebSync Push Framework is displayed as follows.
The following point should be noted:
XXX/request.ashxhave been recorded. These requests are polling requests.
Once processed by the Post-recording wizard, the User Path is modified as follows.
NeoLoad has made the following noticeable changes:
/request.ashxfor 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.
WebsyncVariablesfor example). At the first polling loop, the initial value is calculated in relation to the request that precedes the polling; it is then increment at each loop iteration to reproduce the browser behavior.
WS_idvariable to make the WebSync parameter consistent on every Virtual User iteration.
polling_delaypolling delay is the average of the time intervals between two polling requests in the original User Path.
stop_pollingvariable modifier stops the polling loop by modifying the value of the