NetworkDesign: Difference between revisions
Content deleted Content added
No edit summary |
No edit summary |
||
Line 1:
= Basic idea behind Networking =
The idea behind arianne network protocol is to use a single stream of UDP packets to comunicate server and clients, to allow the different kind of actions we create different types of messages that are then interpreted at the opposite peer.
!!!UDP Packet Format▼
The Network design is based on Messages being transmitted using UDP Packets. There are two types of streams, one is Server to Client and another one that is Client to Server.
Each message is self contained in a SINGLE UDP Packet. There is no mechanism for recovery of lost or repeated messages.
Line 15 ⟶ 14:
*Rest of Message ( up to 1494 bytes )
Each message is contained in one or more UDP Packets, and the UDP Packet format is as follows:
1st UDP Packet is composed of:
*Total number of packets (1 byte)
*Position of this message (1 byte)
Line 24:
*Client ID (4 bytes)
*Rest of Message (up to 1491 bytes)
The following UDP Packets are composed of:
*Total number of packets (1 byte)
Line 29 ⟶ 30:
*Signature of the message (1 byte)
*Rest of Message (up to 1497 bytes)
The idea is to send the serialized message inside several UDP Packets and then rebuild the full message on the Client. There is no kind of error recovery, or retransmission.
Messages are sent from the Server by simply serializing them. So the message itself contains the protocol version, the type of message and the Client id.
Receiving the message is a bit more complex. First we need to determine that we are running a compatible version of the protocol. Once we have agreed that the protocol is compatible we read the type of message and we ask a
!!!Message Types▼
To communicate, the Client and Server of Marauroa use a stream of UDP packets. The message system belongs to the marauroa.common.net package, so refer to code.
We have Client to Server, aka C2S, and Server to Client, aka S2C, messages.
Most messages have two versions of themselves: the C2S and S2C versions.
Communication Model
Line 83 ⟶ 67:
Send Perception ACK Send Perception
--on
Send
Send TranferACK
Send Transfer
--onEvent:
Line 98 ⟶ 84:
Let's discuss in detail each message type.
The login Message is sent from the Client to the Server to request the right to access to the game. The message is composed of a username and password. The Username is a string that is already registered on Server as the name of a user account, and password is a string that is associated with that account. If the username/password combination is correct then Server must send a Login ACK Message to indicate to the Client that the message has been correctly processed. On the contrary, if the username/password is wrong the Server will send a Login NACK.
| |||