Ktor server handler cleanup on client disconnect across engines
I am designing a Ktor server with routes that may remain active for extended periods, such as streaming or long-polling endpoints, and I need to ensure that server-side work stops and resources are released when a client disconnects before the response completes. My uncertainty is whether Ktor provides a uniform contract across its server engines for cancell
ktor