instance

Hi,

I use rti v6.0.0

Im using persistence service. I set the "datawriter durability qos" in my project in "persistent". And i set the xml for that saves datas in file system.

When i unregister an instance that registered before, i expect that the instance won't publish by persistence service even when datawriter that calls dispose destructed and removed from domain. But unexpectedly when i destruct datawriter that caled unregister_instance persistence service publishes that instance from its history.

Say there is a single reader and writer on two separate nodes on a network. The writer is writing a single instance. They are using (automatic) liveness QoS. The application is reading data from the data reader via on_data_available of the DataReaderListener and it has received at least one sample of the instance. Now, there is a network parition. Because of the liveness QoS, the data reader will eventually be notified via on_data_available that the instance is in the NOT_ALIVE_NO_WRITERS state.

Hi all,

I have an application with one DataWriter and one DataReader that catches when an instance is unregistered. It does the following:

- on the publisher side: After all the work is done, the only DataWriter calls unregister_instance() and exits (thus the DataWriter is deleted).