How many times to retry after the first attempt fails retryably.
Zero means one attempt and no more.
Base backoff between attempts, in milliseconds. Doubles per retry.
Backoff is spent inside the request that triggered the delivery, so the caller waits for it — keep the product of this, the doubling, and retries well inside the client's own timeout.
How long a single attempt may take before it is abandoned, in milliseconds.
User-Agent sent on every delivery, so the receiving service can tell
which system is posting to it.
Outbound HTTP delivery settings — how hard an application tries when it posts to a service it does not control.
Remarks
The one settings module with no platform resource behind it. A
fetchto somebody else's endpoint needs a policy just as much as a binding does, and leaving one hard-coded in a service is how a timeout becomes a redeploy.It sits in the kernel rather than an adapter because none of it names a vendor.
Author
Bayu Dwiyan Satria
Version
1.1.0
Since
1.1.0