The Author Online Book Forums are Moving

The Author Online Book Forums will soon redirect to Manning's liveBook and liveVideo. All book forum content will migrate to liveBook's discussion forum and all video forum content will migrate to liveVideo. Log in to liveBook or liveVideo with your Manning credentials to join the discussion!

Thank you for your engagement in the AoF over the years! We look forward to offering you a more enhanced forum experience.

200316 (3) [Avatar] Offline
#1
The Ask/Tell/failure feature could use some clarity.

In chapter 6, page 98 shows a couple of code snippets demonstrating the Ask/Sender.Tell feature. In Fig 6.21, the code calls Sender.Tell(Status.Success). There is no else-Sender.Tell(Status.Failure).

The questions this bring to mind are these.

The implication is that if we don't Tell with Success, there is an implicit Tell with Failure. Is this correct? What happens if there is an exception? Does the 'Ask'er get a response?

I think this section needs a little work. When talking about error handling, the most important question on my mind is how do I tell the user that their request didn't go through?

It would be nice to get some design pattern guidance. I imagine that I have a process manager which submits requests to potentially troublesome actors. When it gets a Failure back, it could then post to a channel/pipeline which will eventually alert the user.
http://www.enterpriseintegrationpatterns.com/patterns/messaging/ProcessManager.html

Is the pattern I've described a good one? Are there better patterns? What are best practices?