Difference between revisions of "Server.met file"

From AMule Project FAQ
Jump to: navigation, search
Line 1: Line 1:
 
== File ==
 
== File ==
  
'''Name:''' ''Server.met''
+
'''Name:''' ''server.met''
  
 
'''Location:''' ''~/.aMule/''
 
'''Location:''' ''~/.aMule/''
Line 7: Line 7:
 
== Description ==
 
== Description ==
  
Binary file containing the list of [[server]]s known to aMule.
+
Binary file containing the list of [[server]]s known to [[aMule]].
  
Because its in binary format, it must be changed within aMule, or with other appropriate tools.
+
Because its in binary format, it must be changed within [[aMule]], or with other appropriate tools.
  
 
The format description below is for development information purposes.
 
The format description below is for development information purposes.
Line 15: Line 15:
 
== Format ==
 
== Format ==
  
Note: all digit filds fields are unsigned unless stated.
+
This file's fields are written in [[little endian]] order.
  
*Met Header (1 Byte): with value Ox0E, and is used in aMule to check for valid server.met files
+
'''Note:''' All digit fields are unsigned unless stated.
  
*Server Count (4 Bytes): lists the number of servers that follow
+
*Met Header (1 Byte): With value ''Ox0E'', and is used in [[aMule]] to check for valid ''server.met'' files
 +
*Server Count (4 Bytes): Lists the number of [[server]]s that follow
 +
*Block of servers: Each [[server]] is constituted by the following fields:
 +
**[[Server]] [[IP]] (4 Bytes): Simply that. The [[server]]'s [[IP]].
 +
**[[Server]] [[Port]] (2 Bytes):  Simply that. The [[port]] through which [[aMule]] will connect to the [[server]].
 +
**Tag Count (4 Bytes): Lists the number of [[server]] tags that follows.
 +
**Block of Tags: Each [[server]] can have a list of associated tags for further information about them. Each tag has the following format:
  
*Block of servers: each server is constituted by the following fields
+
== Example ==
 
+
**Server IP (4 Bytes)
+
 
+
**Server Port (2 Bytes)
+
 
+
**Tag Count (4 Bytes): lists the number of server tags that follow.
+
 
+
**Block of Tags: each server can have a list of associated tags. Each tag as the following format:
+

Revision as of 17:44, 7 June 2005

File

Name: server.met

Location: ~/.aMule/

Description

Binary file containing the list of servers known to aMule.

Because its in binary format, it must be changed within aMule, or with other appropriate tools.

The format description below is for development information purposes.

Format

This file's fields are written in little endian order.

Note: All digit fields are unsigned unless stated.

  • Met Header (1 Byte): With value Ox0E, and is used in aMule to check for valid server.met files
  • Server Count (4 Bytes): Lists the number of servers that follow
  • Block of servers: Each server is constituted by the following fields:
    • Server IP (4 Bytes): Simply that. The server's IP.
    • Server Port (2 Bytes): Simply that. The port through which aMule will connect to the server.
    • Tag Count (4 Bytes): Lists the number of server tags that follows.
    • Block of Tags: Each server can have a list of associated tags for further information about them. Each tag has the following format:

Example