All I have a question concerning client notification and, let's say "guaranteed delivery".
In some of our modules, we have consumers that register interest in modification of keys that are present in Geode. Quite usual, we use the client notifications and "register Interest", and behind the scene, Geode creates a "subscription" that will buffer notifications for this consumer. I am wondering how Geode decide if a notification has been consumed or not by the consumer (and decide to delete the notification from the subscription)? To be more concrete, in a JMS world (or equivalent), this is something you can control with transactions or by manually acknowledging the message. Can we have the same kind of semantics? is this automatic when the CacheListener callbacks end? is it only relying on the subscription-message-tracking-timeout parameter? Thanks for your help. Olivier.
