How many sender contexts/peers do I need in this configuration?
Video server (VS) has streams A, B and C and listens out for video player (VP) connections. VS I assume has one (or more?) rist senders. VP has a rist receiver.
VPs can connect to the VS and view either A, B or C. VPs are in separate locations (IP addresses).
More than one VP can view A, B or C at the same time.
I obviously don't want to send all of A, B and C to each VP as one "flow" and have the VP separate them.
Does VS need to listen on one separate port for each of A, B and C?
If yes, does this require an independent rist sender context per port, or can one sender listen on all ports? I think it can, by creating a peer with "//@:port" for each one? So, if I have a peer per port, how do I send packets from A, B or C to the right peer? Is it something relating to the virt_dst_port?
If no, and I can do it all by having one rist sender context listening on one port, again how do I send packets from A, B or C to the appropriate VP? Can a receiver that "dials-in" provide any information in the initial handshake that could be used to conceptually link it to the stream A, B or C that it requires?
I know I can create a separate rist sender context for each of A, B and C, each set up to listen, and VP just needs to choose the right port to connect to, and this would work, but is that the only way to achieve this set up?