After the recording, a User Path using streaming with the Lightstreamer framework is displayed as follows.
The Lightstreamer streaming request is easily identified, since it ends with the path
Once processed by the NeoLoad Post-recording wizard, the User Path is modified as follows.
NeoLoad has made the following noticeable changes:
/lightstreamer/STREAMING_IN_PROGRESSfor example) has been placed in a loop (
streaming_whilefor example), which continues to loop until the
LS_end_streamingvariable generated by NeoLoad becomes
true(the streaming request can be executed several time if the length of the response is over 300 Kb). Lastly, the loop itself has been placed in a secondary execution thread using a fork action (
LS_end_streamingvariable, with the
falsevalue, to have the streaming function work on every Virtual User iteration.
update-0for example). The
endmessage is added to the streaming request to handle several executions of the streaming request (if the response length is over 300 Kb).
Xrepresents the updated HTML component.
LS_phaseparameter is handled using the
LS_phaseVariable Extractor set on the session creation request (
LS_phase_updatefor example) increments the value of the
LS_phasevariable to reproduce the browser behavior. Lastly, this variable is used in the open streaming request (