AMF polling
After the recording, a User Path using AMF polling is displayed as follows.
AMF polling requests are identified as having a name with the POLL_XXX format.
Once processed by the NeoLoad Post-recording wizard, the User Path is modified as follows.
NeoLoad has made the following noticeable changes:
- All the AMF polling requests have been grouped into a single polling request (POLL for example). This request has been placed in a loop (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). See Polling requests.
- NeoLoad identifies the different types of message returned through the Push channel during recording. These different types of message are modelized by the Push messages (flex.samples.marketdata.Stock or flex.messaging.messages.AcknowledgeMessageExt for example).
- The variable modifier init_polling initializes the NL-stopPolling variable, with the false value, to have the polling function work on every Virtual User iteration.
- The polling_delay is the average of the time intervals between two polling requests in the original User Path.
- The stop_polling variable modifier triggers the exit from the polling loop by modifying the value of the NL-stopPolling variable.