Proper way to end threads?
A protocol agnostic application layer denial of service attack.
Brought to you by:
motoma
Currently using a semaphore, threads die off as a natural consequence of the lack of executable code. However, if a socket were to block, this might not work.
Could issue a os.kill(os.getpid(), signal.SIGKILL), but this would not properly close connections.
Perhaps a combination of both? Separate constructor from execution in the main class, main thread kills all sockets and dies? Sockets would then need to be part of the parent, not local to the individual threads.
Anonymous
This feature has been added to the current release.