Next: Message field implementation
Up: Protocol
Previous: Protocol
Contents
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.

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

- means that the message is of type
and
that it is a message from the server to the client.
- Messages from the client to the server:
- Request for login. Body: uin, password,
nick.
- Send message. Body: destination uin,
message text.
- Add user to contact list. Body: uin, name.
- Remove user from contact list. Body: uin.
- Disconnect. Body: empty.
- Messages from the server to the client:
- Authorize login. Body: empty.
- Login refused. Body: empty.
- Received message. Body: from uin, text.
- Update user status. Body: uin, new status.
- Inform disconnected. Body: empty.
- Push contact. Body: uin, nick.
Next: Message field implementation
Up: Protocol
Previous: Protocol
Contents
Zvika Brakerski
2001-05-09