On Sun, May 4, 2014 at 9:55 AM, Martin Krasser <[email protected]>wrote:
> Hi Heiko, > > > On 03.05.14 06:58, Heiko Seeberger wrote: > > 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. > > > Actor B should send an application-level reply to actor A. Channels > preserve sender references. > Well, that's how I have already implemented it without channels. I was hoping that channels would make that easier ;-) Is it possible to add a feature like a deliverSuccessListener in the future? Thanks Heiko -- >>>>>>>>>> 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.
