Akka persistence module provides at-lease-once message delivery, which means a message may be delivered multiple times. Care must be taken in the application logic to avoid processing the same message more than once. One obvious (to me) way to deal with this is to keep a last-processed-seq-nr in a processor (say A) or view. But a processor may receive ConfirmablePersistent messages from more than one Channel (say X, Y, Z), so A will have to keep 3 'last-processed-seq-nr' variable to keep track events from X, Y, Z respectively. However, I found ConfirmablePersistent interface doesn't expose it channel id, so I don't know how to update these 3 vars?
Did I miss something? If the above logic is correct, will Akka Persistence module do the last-processed-id tracking automatically in the future so we have exactly-once message delivery? -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
