Monitors, upgrading to 5.0: your own Close() under a running callback command ends it in onDone, on the binary API too (tik4net 3a6ce98) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Monitors, testing, upgrading to 5.0: a lost connection reaches the error callback on every transport; the fake's cancel ends in onDone and it refuses an empty parameter name (tik4net 166b44f) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Monitors, testing, upgrading to 5.0: onDone runs only when the command ends without an error (tik4net 4ba7533, X16, D21)
ExecuteListUntilDone off the API: the timeout is honoured, and the async form runs on every async transport (D17) Monitors and streaming, Connection types and capabilities (the Streaming row), CLI transports, Async and cancellation; Upgrading from 4.x to 5.0 and its AI-agent page. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Bounded reads end badly one way: UntilDone's trap classified and its lost connection a TikCommandFatalException; aborts carry the cause; callback loads classify (D10, X9) Monitors and streaming: the abort's InnerException, ExecuteListUntilDone's trap and fatal types, the callback loads' classified error and the onDone overload (compiled sample). Exception handling: the abort and trap rows. Upgrading from 4.x to 5.0 and its AI-agent page: the IOException -> TikCommandFatalException row, the classified traps, the abort's cause; the onDone overload under New in 5.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Streaming reads: a lost connection ends the stream with TikCommandAbortException (tik4net 445546e, X1) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Monitors and streaming: the same-connection caveat links its owner Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Monitors and streaming: new owner page for snapshots, bounded reads, callback monitors and listen Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>