Today subscribers detect publishers via their periodically sent out announce multicast packets. Once such a packet is seen by the subscriber, it sets up a tcp connection to the IP address and port specified in the announce packet.
This process is reliable but non-deterministic since we don't know the timing of the announce packets and if the subscriber, at any given time, has found all available publishers via their announcements.
We need to setup a manual wrapper call around rmc_conn_connect_tcp_by_address() allowing a subscriber to directly connect to a publisher using an IP address and port retrieved from a config file or other external means.
Today subscribers detect publishers via their periodically sent out announce multicast packets. Once such a packet is seen by the subscriber, it sets up a tcp connection to the IP address and port specified in the announce packet.
This process is reliable but non-deterministic since we don't know the timing of the announce packets and if the subscriber, at any given time, has found all available publishers via their announcements.
We need to setup a manual wrapper call around
rmc_conn_connect_tcp_by_address()allowing a subscriber to directly connect to a publisher using an IP address and port retrieved from a config file or other external means.