3 ms·
You pretty much just have to listen for and handle premature closing of the underlying TCP connection. It's the only form of dead peer detection you'll get if
by VWWHFSfQ 3y ago
You pretty much just have to listen for and handle premature closing of the underlying TCP connection. It's the only form of dead peer detection you'll get if someone just abrubtly closes their browser tab.
- teaearlgraycold 3y agoDo server frameworks really require you to think of the TCP connection?
- VWWHFSfQ 3y agoHigh performance servers and frameworks will always have to think about the underlying sockets
- DaiPlusPlus 3y agoNot TCP specifically, but ASP.NET Core binds your controller/action methods' CancellationToken parameter (if present) to HttpContext.RequestAborted - so assuming one uses it correctly (e.g. tying it to things like SQL TRANSACTION/ROLLBACK) then that helps prevent inadvertent changes if the user clicked their browser's Stop button after a POST, or gracefully handle long file upload failures, and so on.