AFS design documents

[AF]

Forgot some

MSG AFS USR username - used to login to the server
MSG AFS BADUSRPASS - A user with this name has already logged in or bad username pass combo
MSG AFS ACCEPTED username - Login accepted
MSG AFS ADDUSR username - message broadcasted signifyign a user joined)

The last one should be replaced at some point. If users are listed in a table then a user being added to the list will cause an update message

http://spring.unknown-files.net/file/34 ... rly_alpha/

Theres the current source code, its a very early alpha, Id like comments on how to proceed from here from a design point of view.

[Tobi]

MSG AFS LOSTUSR username - A user (username) timedout or the connection was lost
MSG AFS RMVUSER username - same as above only the user exited correctly using MSG AFS EXIT

May I suggest keeping consistent names for the messages? Abbreviating USER as USR in some cases but not in others is confusing for client developers.

Actually I'd recommend not abbreviating stuff at all.

[AF]

Agreed, one should not make typos, the latter is USR not USER, however I agree it should be USER not USR, easily changed