EC Protocol HOWTO - Revision history

GonoszTopi: moved EC Procotol HOWTO to EC Protocol HOWTO: Typo in page title

2012-10-16T12:44:17Z

moved EC Procotol HOWTO to EC Protocol HOWTO: Typo in page title

Xoneca: /* Authorization */ Response packet analised

2009-06-29T17:55:31Z

‎Authorization: Response packet analised

Xoneca: Some style applied

2009-01-31T19:55:52Z

Some style applied

Show changes

Xoneca: /* Transmission layer */ 32 bits: from 0 to 31 (not to 32)

2009-01-31T18:58:48Z

‎Transmission layer: 32 bits: from 0 to 31 (not to 32)

82.67.125.160: in search example : op code is uint8 and tag count is uint16, 00 moved in the right place

2008-07-10T21:22:33Z

in search example : op code is uint8 and tag count is uint16, 00 moved in the right place

81.56.207.165 at 10:23, 30 June 2008

2008-06-30T10:23:21Z

83.132.61.252: /* Basic Protocol Structure */

2008-05-09T11:47:22Z

‎Basic Protocol Structure

87.139.115.64 at 11:59, 24 August 2007

2007-08-24T11:59:44Z

87.139.115.64 at 17:18, 21 August 2007

2007-08-21T17:18:24Z

87.139.115.64: extend short description

2007-08-21T16:51:00Z

extend short description

@@ Line 98: / Line 98: @@
 This is a packet in hex values that is sent to aMule for authorization:
 <pre>
-00 00 22             // flag
+00 00 22             // flags (UTF-8 compression)
-00 00 36             // packet body length 54
+00 00 36             // packet body length (54 bytes)
                       // EC_OP_AUTH_REQ
-                      // tag count
+                      // tag count (4 bytes)
 c8 80                   // EC_TAG_CLIENT_NAME
                       // EC_TAGTYPE_STRING
-d                      // value length 13
+d                      // value length (13 bytes)
 6d 75 6c 65 2d 72 65 6d 6f 74 65 00 // "amule-remote\0"
 c8 82                   // EC_TAG_CLIENT_VERSION
                       // EC_TAGTYPE_STRING
-                      // value length 7
+                      // value length (7 bytes)
 78 30 30 30 31 00    // "0x0001\0"
                       // EC_TAG_PROTOCOL_VERSION
                       // EC_TAGTYPE_UINT16
-                      // value length 2
+                      // value length (2 bytes)
 00                   // value is defined by EC_CURRENT_PROTOCOL_VERSION
                       // EC_TAG_PASSWD_HASH
                       // EC_TAGTYPE_HASH16
-                      // value length 16
+                      // value length (16 bytes)
 bc e5 c7 4f 58 9f 48 // md5 hashed password string
 db d5 7e 9c a9 f8 08 // password "aaa" was used
@@ Line 126: / Line 126: @@
 <tt>c8 80</tt> is in fact an UTF-8 encoded number. It decodes to <tt>02 00</tt> (or 512 in decimal). As every tag code, it is shifted one bit to left to fit in a bit that indicates the presence of subtags. The lowest bit of <tt>02 00</tt> is <tt>0</tt>; so this tag doesn't have subtags. When we shift the value to the right one bit (or divide by 2), we get <tt>01 00</tt>. That's the value that can be found in ECCodes.h.
 === Search request ===

@@ Line 53: / Line 53: @@
 :bits 7,15,23: Extension flag, means that the next byte of the flags is present.
-:bits 8-14,16-22,24-32: Reserved for later use.
+:bits 8-14,16-22,24-31: Reserved for later use.
@@ Line 63: / Line 63: @@
 :Note 2: Bits marked as "reserved" should always be set to 0.
 == Application layer ==

@@ Line 186: / Line 186: @@
 00 00 21 //message length: 33
-00	//EC_OP_SEARCH_START
+	//EC_OP_SEARCH_START
-	//tag count
+01	//tag count
 e 03	//EC_TAG_SEARCH_TYPE
 	//EC_TAGTYPE_UINT8

@@ Line 89: / Line 89: @@
 ::[ec_taglen_t] TAGLEN
 ::<[uint16] TAGCOUNT>?
-:::<sub-tags>
+:::&lt;sub-tags&gt;
 :::<tag data>

@@ Line 11: / Line 11: @@
 a high level application layer.<br>
-The transmission layer consist of an two int32 values.<br>
+The transmission layer consist of two int32 values.<br>
 A uint32 flag specify the format of the message e.g. if the packet uses utf8 encoded numbers or is compressed by zlib.<br>
 The next uint32 determines the size of the application layer data.<br>

← Older revision	Revision as of 12:44, 16 October 2012
(No difference)

← Older revision		Revision as of 11:59, 24 August 2007
Line 118:		Line 118:
	*no more \0 for string termination		*no more \0 for string termination
	*last bit of flag byte indicates a following flag byte, and so on		*last bit of flag byte indicates a following flag byte, and so on
		+
		+
		+	== Resources ==
		+
		+	You get definitions of OP- and Tag-Codes at this locations in the source:
		+	*./src/lib/ec/[c#\|cpp\|java]/ECCodes.[cs\|h\|java]
		+	* ./docs/EC_Protocol.txt (outdated, but much useful information)

@@ Line 112: / Line 112: @@
-'''Future Changes'''
 Future changes of the EC protocol (probably after 2.2.0) may be:
 *no more \0 for string termination
 *last bit of flag byte indicates a following flag byte, and so on
-'''Examples'''
 This is a packet in hex values that is send to aMule
@@ Line 157: / Line 170: @@
 That's the value that can be found in ECCodes.h.
 This is a search request that

@@ Line 8: / Line 8: @@
 Short description:
-:EC protocol consist of two layers: a low-level transmission layer, and
+EC protocol consist of two layers: a low-level transmission layer, and
-:a high level application layer.
+a high level application layer.<br>
 == Transmission layer ==