After the record, a User Path using polling with the Lightstreamer Framework is displayed as follows.
The following point should be noted:
XXX/bind_session.js
have been recorded. These requests are polling requests.Once processed by the NeoLoad Post-recording wizard, the User Path is modified as follows.
NeoLoad has made the following noticeable changes:
polling_while
for example), which continues to loop until the NL-stopPolling
variable generated by NeoLoad becomes true
. Lastly, the loop itself has been placed in a secondary execution thread using a fork action (push_fork
for example). For more information, see Polling requests.init_polling
initializes the NL-stopPolling
variable, with the false
value, to have the polling function work on every Virtual User iteration.initialSnapshot-1
or update-1
for example).initialSnapshot-X
, update-X
and heartbeat
, where X
represents the updated HTML component.LS_phase
parameter is handled using the LS_phase
Variable Extractor set both on the session creation request (creation_session.js
for example) and on the Push request (/lightstreamer/bind_session.txt
for example). A JavaScript action (LS_phase_update1
for example) increments the value of the LS_phase
variable at each loop iteration to reproduce the browser behavior.polling_delay
polling delay is the average of the time intervals between two polling requests in the original User Path.stop_polling
variable modifier stops the polling loop by modifying the value of the NL-stopPolling
variable.