Message types

Our protocol is build in a way that is very easy to extend. This is before the message types are assigned in hierarchal order so you could very easily add a completely new class of messages to the protocol.

The convention of the messages is as follows:

Preliminaries:

Predefined constants.

$100+x$

means that the message is of type $x$ and that it is a message from the client to the server.

$200+x$

means that the message is of type $x$ and that it is a message from the server to the client.

Messages from the client to the server:

$100+$

• $1$ - Request for login. Body: uin, password, nick.

• $2$ - Send message. Body: destination uin, message text.

• $3$ - Add user to contact list. Body: uin, name.

• $4$ - Remove user from contact list. Body: uin.

• $5$ - Disconnect. Body: empty.

Messages from the server to the client:

$200+$

• $51$ - Authorize login. Body: empty.

• $61$ - Login refused. Body: empty.

• $2$ - Received message. Body: from uin, text.

• $3$ - Update user status. Body: uin, new status.

• $4$ - Inform disconnected. Body: empty.

• $7$ - Push contact. Body: uin, nick.