Juhana Helovuo

The DDS and RTPS specifications mention type `BuiltinTopicKey_t`. See e.g. Table 8.6 - RTPS Entity Attributes in RTPS Spec 2.5. Its exact contents, definition, and meaning are a bit mysterious....

The current module structure historically derives from the structure of DDS and RTPS specifications, which is not ideal for (this) implementation. Planned changes: * Split current `dds` module into two:...

Find `unwrap()` and `expect()`calls and eliminate them

4

Either replace with more graceful error-handling or write comments to justify why panic cannot occur.

Implement `wait_for_acknowledgments`

2

DDS Spec 2.2.2.4.1.12 wait_for_acknowledgments https://github.com/jhelovuo/RustDDS/blob/37fdd1c21eb4103c4e7d0a1d97627f4f3d259d91/src/dds/pubsub.rs#L285 and DDS Spec 2.2.2.4.2.15 wait_for_acknowledgments https://github.com/jhelovuo/RustDDS/blob/37fdd1c21eb4103c4e7d0a1d97627f4f3d259d91/src/dds/with_key/datawriter.rs#L333

Implement remaining Communication Status events

1

These are from DDS Spec 2.2.4.1 Communication Status (table) Topic * INCONSISTENT_TOPIC Subscriber * DATA_ON_READERS - not necessary, as operation is `poll()` -based anyway. DataReader * SAMPLE_REJECTED * LIVELINESS_CHANGED *...

Large parts of Topic discovery (independent of remote Reader/Writer discovery) is missing. E.g. local Topic creation is not broadcast at all, unless we have Reader or Writer on it.

DDS Spec 2.2.3.13 PARTITION