Provide transient message operations

[tomkerkhove]

Provide transient message operations to handle temporary failures when completing a message, etc.

[stijnmoreels]

Somre more guidance for this issue is proparly required. What is considered a 'temporary failure'? How should it be handled?

The message pump has now something of a handling logic, but it's in my opninion a bit too high-level to be useful.

[tomkerkhove]

When we want to complete the message in a handler and it fails with Server too busy or time out, that we retry it x times

[stijnmoreels]

OK, cool, after #141 is done, we can maybe create some options a consumer can configure on the message router.

[stijnmoreels]

Except of course if you mean the RetryPolicy on the MessageReceiver (and in the future ServiceBusReceiver); in that case it can be a set of values configured on the options of the message pump.
This is again something that we may want to hold off until we've migrated to these new types.

[tomkerkhove]

Adding retry on operations such as deadletter, etc would be enough indeed; but would need to be opt-in/out indeed with configurable retry count/wait time

[stijnmoreels]

Can we use the ServiceBusRetryOptions for this?

[tomkerkhove]

Fine by me

[stijnmoreels]

By default, the ServiceBusClient has a exponential retry with a time-out of 1min and max retry of 3.