CleanAddressSvc reaches its consumers indirectly: SAIF.Services — the class library that carries the reference and ships in the SAIF.SAIFCode.Core NuGet package — exposes three public adapter types over the proxy, but no production code in this repository constructs the adapters or the proxy itself.
No — this repository's own app.config is not loaded by a consuming host; an override requires the host to redeclare applicationSettings/SAIF.Services.Properties.Settings/SAIF_Services_CleanAddressSvc_clsCAServices*
None configured — WebClientProtocol default of 100,000 ms applies*
No
—
Yes
Retry
None configured
No
—
Yes
Circuit breaking
None configured
No
—
Yes
Thread safety
Not determined from source
—
—
No
Cancellation
Not supported — no cancellation on any call site
—
—
Yes
Message size limits
None set — ASMX transport defaults apply
No
—
No
Every call site is synchronous with no retry, timeout, or cancellation configured. A consumer that needs to bound the call latency or recover from a transient failure must wrap the adapter itself; nothing in SAIF.Services provides that. Cross-reference Tech debt findings TD-CA-02 and TD-CA-03.
// CleanAddressServiceBase.cs:26-39 (paraphrased structure, see source for exact IDisposable pattern)protectedvirtualvoidDispose(booldisposing){if(disposing){UspsService.Dispose();}}
Note: Statements marked with † are derived from dependency library
documentation via the Legends CLI. Statements marked with * were inferred
from code structure or contextual evidence.