summaryrefslogtreecommitdiff
path: root/docs/Messenger_Protocol.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/Messenger_Protocol.txt')
-rw-r--r--docs/Messenger_Protocol.txt33
1 files changed, 0 insertions, 33 deletions
diff --git a/docs/Messenger_Protocol.txt b/docs/Messenger_Protocol.txt
deleted file mode 100644
index dc92c303..00000000
--- a/docs/Messenger_Protocol.txt
+++ /dev/null
@@ -1,33 +0,0 @@
1Protocol for messages, data, etc..
2
3Streaming audio/video will not use this protocol as they can absorb some data loss.
4
5The protocol itself will run on top of the encryption which means it should be
6impossible for someone to know what type of data is being transmitted.(Well they
7could just analyze how much data is being transmitted for a pretty good guess)
8
9Because it runs on the encryption which itself runs on our Lossless UDP protocol
10it can be guaranteed that no data will be lost.
11
12Basic packet format:
13[char data_id][data]
14
15data_id represents the type of data.
16
17All strings must be UTF-8.
18
19EX: data_id 64 designates a chat message. so the packet would look like: @Hello WorldNULL
20Where @ is the ASCII character for 64, "Hello World" is the message and NULL is the null string terminator.
21
22Proposed data_ids and what they mean (in decimal)
23
24ids 0 to 16 are reserved.
25
2648 Username (Send this packet as soon as you connect to a friend or to each friend everytime you change names.
27 Username is maximum 128 bytes long with the null terminator included)
28
2949 Status change
30
3164 Chat message
326? File transmission.
33