The challenge here is that the HTTP request is essentially a synchronous RPC from the perspective of the client. The architecture you've described is pretty by-the-book for request/response style unit-of-work: if it fails, error is returned to the client. I wouldn't go out of your way to change it for this one problem.
My recommendation for this would be to capture this specific error for this specific HTTP request and return some friendly error to the user/client. Something like "this user already exists" or whatever is relevant for your problem. Then let the user/client retry the request. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To view this discussion on the web visit https://groups.google.com/d/msg/nhusers/-/m0IVdSFJTBQJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
