Tristan B. Velloza Kildaire 2305c19623 Client ... - Added an overridable `onConnectionClosed()` that is called when the connection is closed by either us or the remote host - Added `closedConnectionHandler()` (gonna get rid of soon) - Calling `disconnect()` will now RATHER shutdown the socket than close it, it no longer performs any other sub-systems clean up - Implemented `doThreadCleanup()` which stops the receive and send managers, stops the eventy engine too - At every `read()` we do in the reader loop, check if the return value is `<0` or `==0` in which case set the running state to false and exit the loop - The exiting of the reader loop will now shutdown the socket (in case remote host caused it and not us (via `disconnect()` for example) ), `close()` the socket and call `doThreadCleanup()`		2023-06-27 20:08:16 +02:00
..
birchwood	Client	2023-06-27 20:08:16 +02:00