Top  Previous  Next

The collection of potential senders.

property Senders: TRVSenderCollectionEx;

This collection works differently depending on the side which initiates a connection.

Option 1: Connection from TRVCamSender to TRVCamReceiver

This type of connection happens if Protocol=rvpUDP, or TCPConnectionType=rvtcpSenderToReceiver.

Senders are used as filters defining which connections can be accepted.

Each item (TRVSenderItemEx) in Senders specifies which connections can be accepted from the address specified in item.SenderHost. If the item has non-empty GUIDFrom, the receiver accepts only senders having the same value of GUIDFrom. If item.GUIDFrom is empty, the item properties AudioSenders, VideoSenders, UserDataSenders, CmdSenders, FileSenders are used as filters (however, these properties make more sense when communicating with TRVMediaServers, see below).

If Senders is empty, connections from any senders are accepted.

Option 2: Connection from TRVCamReceiver to TRVCamSender

This type of connection happens when Protocol=rvpTCP (or rvpHTTP), and TCPConnectionType=rvtcpReceiverToSender.

The receiver connects to all senders listed in Senders. For each item, the receiver connects to the address item.SenderHost:item.SenderPort. To make a successful connection, item.GUIDFrom must be equal to sender.GUIDFrom.

Option 3: Connection from TRVMediaServer to TRVCamReceiver

The following settings are required for this mode: Protocol=rvpTCP (or rvpHTTP), and TCPConnectionType=rvtcpReceiverToSender.

In general, properties should have the same settings as with the option 2. However:

item.SenderHost must specify the server address

item.GUIDFrom should be empty,

the item properties AudioSenders, VideoSenders, UserDataSenders, CmdSenders, FileSenders may contain lists of clients allowing to send data to this receiver; if they are empty, data from all clients of this server are accepted.