After the recording, a User Path using AMF streaming is displayed as follows.
AMF streaming requests are identified as having a name with the
<path> open and
<path> close formats.
Once processed by the NeoLoad Post-recording wizard, the User Path is modified as follows.
NeoLoad has made the following noticeable changes:
/samples/messagebroker/streamingamf openfor example) has been placed in a secondary execution thread,
/samples/messagebroker/streamingamf closefor example) tells the server to stop Push. Upon receiving the request, the server closes the streaming request
/samples/messagebroker/streamingamf open, allowing NeoLoad to move on to the next action. There are no other actions in the
push_forkobject so the secondary thread ends.