RTMP channels are requests with special characteristics:
The way these requests behave has an impact on the User Path design:
At the end of the recording, NeoLoad detects the presence of the RTMP channel and offers to create a new version of the User Path. This is an example of a User Path created with an RTMP channel:
RTMPChannel_1 logical action is used to execute the RTMP channel in a secondary execution channel in the User Path. For more information, see Fork.
NeoLoad natively handles Push technologies, including RTMP. For more information about the Push technologies supported by NeoLoad, see Push frameworks and RTMP streaming. For more information about streaming, see Streaming requests.