Ye Li

Hi. Or maybe what I'm describing is a bit confusing， I will try to explain again > If you want to have processes A1, A2 and B1 all exchanging data...

> The most important question is (in my opinion): do you need to have a flexible sized datatype in your topic? Because, if you know the (maximum) size of the...

> Hi @YeahhhhLi , I think there may be something else going on here. Looking at what you have written: > > > 1. shm needs iox service and config,...

> I quickly made this example program, to show how to "automatically fit" runtime defined numbers of points into the smallest fixed size types. I hope it is of use...

> In fact, we only have one process, and it may be deployed on two hosts in the future. At that time, both inter-process communication and cross-host communication are required....

> A topic's name needs to be unique on the domain it is created on, so your example will not work. lol yes u r right, i missed this， let's...

@reicheratwork Thank you for your patience I will try to test again !

> Maybe using some non-fixed size datatypes would be a better solution in your case then, as this will allow you to use a single topic to exchange all possible...

> looking at the dds_write_impl function (called by dds_write) OK, I'll take a look in a while > an additional copy step. This does introduce additional overhead, iceoryx's zero-copy feature...

> Looking at this, setting the historykind to KEEP_ALL will preclude the use of SHM. Wouldn't it be better to have the same QoS settings for the publisher program, and...