Dear all, is something like a LastUniqueKeySubscriptionRecoveryPolicy available or in the making? Possibly with some means to identify as well a final deletion message via a query syntax similar to the QueryBasedSubscriptionRecoveryPolicy? Or alternatively as an addendum to the TimedSubscriptionRecoveryPolicy?
I'm asking because this is an important feature of DDS, and we are currently comparing DDS and ActiveMQ for potential future use in Air Traffic Managements applications. We have for instance track and flightplan object producers and consumers, and whilst tracks are updated every 5 seconds, flightplans can linger in the system for some time after initial creation without being updated, and a consumer must upon restart be able to recover all the latest flightplan messages for every individual flight ... Sorry for posting this earlier in ActiveMQ-User, but there nobody replied to my question within reasonable time ... Kind regards, Sebastian -- View this message in context: http://activemq.2283324.n4.nabble.com/LastUniqueKeySubscriptionRecoveryPolicy-tp4675581.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
