unregister

Hello,

My scenario involve a datawriter and a datareader each one runs on its own host and exchanging topic instances through network.

I want the datareader side to be able to:
- Allocate resources (working processes for example) on creation of instances because the datawriter issues write keyed samples
- Free the resources on destruction of instances because the datawriter issues unregister or dispose (doesn't matter) of keyed samples, once they are created

Until now, no difficulty by reading status instances on the datareader side.

Hello,

I want to achieve some kind of redundancy using keyed topics and exclusive ownership. Therefore I have multiple writers for the topic each with a different strength.
When the writer with the highest strength unregisters its instance, I want the readers to be notified and they should then read the highest strength instance alive.

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).