Will this approach lose other features besides content filter? #3498
Replies: 1 comment
-
Hi @x9527x1024x, Dynamic Types feature allows for generating the required Type Support for serializing/deserializing the data at runtime instead of being completely defined at build time. This feature does not include the type evolution which is considered in the XTypes specification. Currently, Fast DDS supports Dynamic Types (though with several known issues, which are being fixed right now), but type evolution is not yet supported. Consequently, modifying your data type will cause to lose communication with applications that uses the first version of your data type. Also, as you state in your comment, if you have configured a Content Filtered Topic using the TypeObject of the first data type, this filter will be invalid if the TypeObject is modified. |
Beta Was this translation helpful? Give feedback.
-
Hey guys,
I have a question about dynamic data structure.
Assuming we have a data type called movie, it was defined by movie.idl as below
struct movie {
string name;
int32 id;
sequence actor_list;
};
then create the DynamicData_ptr of movie.idl. then use the DataWriter->write(void*) to send the data.
Next,let's modify the movie.idl, put all members into an octet array.
struct movie {
octet info[100];
};
I know, use the following structure, just have one member octet will lost the content filter features.
And, Will other features be lost?
Beta Was this translation helpful? Give feedback.
All reactions