Talk:Ed2k URI scheme

Source

This article is imported from Everything2.

http://www.everything2.com/index.pl?node_id=669790
—Preceding unsigned comment added by Paranoid (talk • contribs) 17:57, October 9, 2003 (UTC)

Some things that should be noted:

ed2k URIs inproperly use // after the colon. This is incorrect.

There is another URI specification in the works that is not network or protocol specific. See http://magnet-uri.sf.net/ for more information.

-- CortlandKlein —Preceding unsigned comment added by 66.33.205.13 (talk) 21:35, December 19, 2004 (UTC)

to be edited into article..

eD2k links

eD2k links are links which refer to some file or server in the eD2k network.

They have the follwing format:

ed2k://|TYPE|REST-OF-FIELDS|/

Note that each field is separated from the others by a pipe character (|).

This are the meanings of each field:

• ed2k:// -> This is the protocol handler. It shows that the link refers to an eD2k file.
• TYPE -> This indicates the kind of link it is. It's value might be file when it refers to a file, or server when it refers to a server.
• REST-OF-FIELDS -> This fields will depend on the type of link it is (describbed below).

File links

This links add a file to your download list.

They have the follwing format:

ed2k://|file|NAME|SIZE|MD4 hash checksum |/

• NAME -> This will contain the name of the file the link is refering to.
• SIZE -> This field contains the size of the file in bytes.
• MD4-HASH -> This field contains the MD4-Hash of the file.

Aditionally, some other fields can be added after the MD4-HASH field. Here are some (these fields are extensible depending on the client you are using):

• PartHashes -> It will show the MD4 hash of each chunk in the file. It's format is p=hash1:hash2:hash3 with as many hashes as the file needs.
• Sources -> It informs about possible known sources of the file. It's format is "sources,IP:Port,IP:Port,IP:Port" with as many sources as desired. Note that a hostname may be specified instead of an IP address. Also note that that source fields differ from other types of fields, see the syntax in the example below.
• URLs -> It may happen that the file in the link can be downloaded from some URL. In such cases, it can be told in the link by putting a field like s=URL and if more than one URL must be written, each will be indicated in a separate field.
• Root Hash -> The Root Hash of the file (please read about AICH to know what a Root Hash is) may be specified in the link by putting a filed like h=RootHash

Examples:

ed2k://|file|NAME|SIZE|MD4-HASH|p=HASH1:HASH2:...|/
ed2k://|file|NAME|SIZE|MD4-HASH|h=HASH|/
ed2k://|file|NAME|SIZE|MD4-HASH|/|sources,<IP:Port>,<IP:Port>,...|/

Server links

This links add a server (the specified server in the server link) to your serverlist.

They have the follwing format:

ed2k://|server|IP|PORT|/

• IP -> IP of the server to connect to.
• PORT -> Port where the server is listening for incomming eD2k connections

Serverlist links

This links add a whole serverlist to your current serverlist if you had one. It will just be used as your serverlist if you had no previous serverlist.

They have the follwing format:

ed2k://|serverlist|ADDRESS|/

• ADDRESS -> Full address to the serverlist file (including the serverlist's filename).

—Preceding unsigned comment added by Leuk he (talk • contribs) 09:00, October 12, 2006 (UTC)

Are ed2k://|nodeslist|address|/ and ed2k://|search|terms|/ URIs also part of standard ed2k protocol, or are eMule specific? Xoneca (talk) 23:59, 24 April 2012 (UTC)

I think I have compiled all possible params (for a file link) in a single URI: (Brackets mark optional parts)

ed2k://|file|<file name>|<size>|<hash>|[s=<url>|][h=<AICH root hash>|][p=<part1 hash>:<part2 hash>:...|][/|sources,<host>:<port>[,<host>:<port>[,...]]|]/

Xoneca (talk) 00:40, 25 April 2012 (UTC)

URI?

I'm no expert, but isn't it supposed to be URL? 2A02:C7C:36EB:D400:D1F8:7F09:FCF:BDA1 (talk) 07:44, 1 October 2023 (UTC)