that what I just want. I am still wondering should there be an deliveryConfirmedListener just as redeliverFailureListener.by this way,I will make my life easier. I don't think the application-level replay should be a answer for that replay could be lost and there have one internal ACK in the channel itself ,why not just use it?
for the design ,I think some API may should be symmetrical. 在 2014年5月3日星期六UTC+8下午12时58分18秒，Heiko Seeberger写道： > > Hi, > > A short-lived actor A should send a "result" message to some other actor B > before it terminates itself. As it is important that this message gets > delivered, I would like to use a channel in order to retry message > delivery. In case of permanent delivery failure (redeliverMax exceeded) the > short-lived actor A would send the message to some other actor C which > would know what to do. This can be implemented using a > redeliverFailureListener. > > My question is: How can the short-lived actor A know that the message has > been delivered, i.e. the ConfirmablePersistent message has been confirmed? > AFAIK there's no deliverSuccessListener or such. > > Thanks > Heiko > > -- > > Heiko Seeberger > Twitter: @hseeberger > Blog: blog.heikoseeberger.name > -- >>>>>>>>>> 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 akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
