User management is an important feature for any communication platform. The SockTalk protocol needs to be updated to include kicking and banning users (IP addresses).

Storing the IP address associated with each client handler is useful anyway.

Currently, all work initializing the server and client occurs right in the constructor. This makes it hard to use the library in GUI frontends, as the application can be in a running but disconnected state.

In the Swift framework, this work is done in callable initialization functions. This allows the code to be run when the user is ready.

When users are kicked, they still receive a “disconnected” message, but with no username. After being sent the TERM message, they shouldn’t receive any more data.

If the SockTalk protocol is to be used for sending state data in games, the addition of a UDP mode might be in order.

This could reduce latency for streams of data that don’t need TCP reliability.

Currently, the client handler constructor code reads from the socket to obtain the desired username of the newly connected user. However, this is a blocking operation and means that the accept thread will be blocked indefinitely if the new connection simply refuses to send a username.

This should be fixed by:

• Adding a timeout so connections that don't send a username (and thus violate the protocol) are dropped
• Moving the username check out of the constructor or at least letting an asynchronous code block execute it such that the accept thread isn't blocked