summaryrefslogtreecommitdiff
path: root/docs/Messenger_Protocol.txt
diff options
context:
space:
mode:
authorirungentoo <irungentoo@gmail.com>2013-07-01 15:17:09 -0400
committerirungentoo <irungentoo@gmail.com>2013-07-01 15:17:09 -0400
commita10a4aaa9614e045f48ea3cf1af961300766cf49 (patch)
treef62c3af12c5e60985dbc0b9141ff11280d1c8782 /docs/Messenger_Protocol.txt
parent62839f1bd95b2dfc43cffd7dfa8b1326cc87ef8b (diff)
Added basic draft of the messenger protocol.
Diffstat (limited to 'docs/Messenger_Protocol.txt')
-rw-r--r--docs/Messenger_Protocol.txt29
1 files changed, 29 insertions, 0 deletions
diff --git a/docs/Messenger_Protocol.txt b/docs/Messenger_Protocol.txt
new file mode 100644
index 00000000..9362fdd2
--- /dev/null
+++ b/docs/Messenger_Protocol.txt
@@ -0,0 +1,29 @@
1Protocol for messages, data, video, etc..
2
3The protocol itself will run on top of the encryption which means it should be
4impossible for someone to know what type of data is being transmitted.(Well they
5could just analyze how much data is being transmitted for a pretty good guess)
6
7Because it runs on the encryption which itself runs on our Lossless UDP protocol
8it can be guaranteed that no data will be lost.
9
10Basic packet format:
11[char data_id][data]
12
13data_id represents the type of data.
14
15EX: data_id 64 designates a chat message. so the packet would look like: @Hello WorldNULL
16Where @ is the ASCII character for 64, "Hello World" is the message and NULL is the null string terminator.
17
18Proposed data_ids and what they mean (in decimal)
19
20ids 0 to 16 are reserved.
21
22
2364 Chat message
2465 Audio Data(Voip)
2566 Video?
2667 File transmission.
2768
2869
29...