Geode currently does not support pure messaging semantics; where events are removed from the messaging system as soon as its delivered to intended recipients (one or all)....
As you read It sends it to all the subscribed client...You may have to add your own logic do so...May be have one client (with redundancy) subscribing; and when the event/callback has received, send it to other clients in round-robin way (or some other)... May be there could be other solutions... -Anil. On Mon, Aug 15, 2016 at 8:42 AM, Chaudhary, Sushil (CONT) < sushil.chaudh...@capitalone.com> wrote: > All, > I can see Geode working as reliable messaging, all client subscribe to > the cache will get a call back with the key,values put into the cache. So, > Typically it works as TOPIC mode, that means, same message is delivered to > call client. Is there any way, I can make it work in QUEUE mode (not > TOPIC), that means, if one client gets a callback for a cache event, that’s > it. Other client should get callback for next message, not the same. > Actually I am trying to take benefit of parallel processing of message by > multiple clients. > > https://cwiki.apache.org/confluence/display/GEODE/Reliable+Messaging > > Please let me know. > > *Sushil Chaudhary* > > *Email*: sushil.chaudh...@capitalone.com > > ------------------------------ > > The information contained in this e-mail is confidential and/or > proprietary to Capital One and/or its affiliates and may only be used > solely in performance of work or services for Capital One. The information > transmitted herewith is intended only for use by the individual or entity > to which it is addressed. If the reader of this message is not the intended > recipient, you are hereby notified that any review, retransmission, > dissemination, distribution, copying or other use of, or taking of any > action in reliance upon this information is strictly prohibited. If you > have received this communication in error, please contact the sender and > delete the material from your computer. >
