namespace ZB.MOM.WW.OtOpcUa.Core.Abstractions;
///
/// Optional companion to for a driver whose upstream can ACCEPT an acknowledge
/// without CONFIRMING it was applied (lmxopcua#869). mxaccessgw answers its AcknowledgeAlarm RPC OK
/// both when the AckMsg write was applied and when it was only sent with no completion observed; the
/// truth arrives later, as the alarm's own acknowledged transition on the alarm stream.
///
///
///
/// The runtime calls after
/// returned normally, with the SAME request instances, OUTSIDE the resilience pipeline (it is a wait on an
/// upstream event, not I/O, so it must neither be cut by the capability timeout nor count toward the
/// breaker) and OFF the driver actor's mailbox (the wait is seconds long).
///
///
/// It completes normally when every request is confirmed, or never needed confirming (the upstream
/// reported it applied). It throws — normally a naming why —
/// when an acknowledge is not confirmed within the driver's own bounded window; the runtime then reverts
/// the condition to unacknowledged exactly as it does for an
/// failure (lmxopcua#760). The window is the driver's to own and bound.
///
///
public interface IAlarmAcknowledgeConfirmation
{
/// Waits for the upstream to confirm the acknowledges sent.
/// The request instances previously passed to .
/// Abandons the wait (the caller then treats the acknowledge as unconfirmed).
/// A task that completes when every acknowledge is confirmed or needed no confirmation.
Task ConfirmAcknowledgedAsync(
IReadOnlyList acknowledgements,
CancellationToken cancellationToken);
}