I meant in case we have a blocking situation. Of course a socket read timeout will eventually release the blocking.
I didn’t look closely at the async implementation. But I’d guess it’s just async over a socket that block on reading? > Am 17.12.2025 um 17:57 schrieb David McClain <[email protected]>: > >> DDoS in a way that when the receiver blocks it blocks a thread and either >> you can’t receive anything anymore on other connections. >> Or it will consume a ton of other threads which may all block. >> > > ??? I don’t understand what you are trying to say here. > > I cannot imagine a situation in which my Async Sockets get blocked in that > manner. And the self-sync protocol will not get tangled up on any inputs. > Errors simply cause the self sync to scan forward, dropping all, until it > recognizes another start-sync sequence. > > ——————— > FWIW, you care welcome to peruse my implementation of Async Sockets and > self-sync protocol here: > > https://github.com/dbmcclain/Lisp-Actors/tree/main/xTActors/secure-channel
