I learned from this page that multicast transport cloud be used by specifying multicast_ip for reader one by one.
That means multicast transport is actually statically assigned.
I wonder if there is some way to let the writers&readers use multicast transport and know each other automatically.
For example, a writer randomly choose a multicast_ip:port and then tells its readers.
Then the readers begin to join that multicast group and recv msgs.
Unfortunately, what you asked about isn't exactly supported.
There is something called a multichannel DataWriter, in which different substreams of a Topic can be sent on different multicast addresses for DataReaders of the topic that are using content-filters to subscribe to a substream of the data (based on values of data members).
But you still have to configure each DataWriter with explicity multicast address/port values.
Please see these links for documentation:
https://community.rti.com/static/documentation/connext-dds/7.3.0/doc/manuals/connext_dds_professional/users_manual/users_manual/MULTI_CHANNEL_Qos.htm?Highlight=multichannel
https://community.rti.com/static/documentation/connext-dds/7.3.0/doc/manuals/connext_dds_professional/users_manual/users_manual/MultichannelDatawriters.htm#multichanneldatawriters_462002162_216998
https://community.rti.com/static/documentation/connext-dds/7.3.0/doc/api/connext_dds/api_cpp/structDDS__MultiChannelQosPolicy.html
Ok. Thank you!
Hi,
Actually, there may be something that does what you want.
Please take a look at the TransportMulticastMapping QoS Policy...you set it for a DomainParticipant.
https://community.rti.com/static/documentation/connext-dds/7.3.0/doc/manuals/connext_dds_professional/users_manual/users_manual/TRANSPORT_MULTICAST_MAPPING_Qos.htm
https://community.rti.com/static/documentation/connext-dds/7.3.0/doc/api/connext_dds/api_cpp/structDDS__TransportMulticastMappingQosPolicy.html#details