WaitOptions

The tuning of waits on one node; the node itself, as signals address it, is its WaitCoordinator's origin.

• maxTimeout caps the timeout a caller asks for.

• maxHops is the longest chain a wait may follow: DEFAULT_MAX_HOPS by default, at most MAX_HOPS_CAP. Each saga a chain follows adds two hops, its handled and the next committed.

• unknownContexts is what a chain may name of a context this node knows no Manifest of.

• defaultTimeout is the timeout of a command whose caller names no wait plan, capped by maxTimeout as any other; me.ahoo.wow.runtime.admission.CommandGateway applies it to every entry.

• maxRegistered is how many waits the node holds at once: DEFAULT_MAX_REGISTERED by default. A command whose wait would be one more is not run: it is answered FAILED at ACCEPTED with ResultCodes.BUSY (wow.command.busy, 429 with Retry-After), as a command beyond the node's in-flight limit is, so a retry with the same request id is safe. A plan answered at ACCEPTED registers no wait and is never refused so.

Fields may be added: Wow builds it from the host's configuration, so the constructor is internal to Wow.