There are several ways to distribute your content using eDonkey.

Sharing: The simplest way is to just share your content by going to the shared tab in the application. People can then search for and find your content.

ed2k Links: If you want to allow people to click on a link in a web page or email to get your content then you can make donkey links. These are like normal html links except that they start the file downloading inside overnet. This means you don't have to store the file on a webserver. You just have to make sure that there is an overnet client running somewhere that is sharing the linked to files.

You can make ed2k links by right clicking on files in search results, transfers, or shared and selecting "copy link to clipboard".

Here is an example of an ed2k link:
ed2k://|file|overnet0.50.1.exe|1225593|9aceac18177fc86d18be5e1c19750408|

Links with http: In the ed2k link you can also include a URL of where the file can be found as a normal http download. This will cause overnet to not only download the file from the overnet network but also from the webserver. This allows you to get the benefits of lowered bandwidth without running an overnet client. If you already are distributing your content through a webserver then you can simply make ed2k links with the existing URLs.

Http with links: If you would like to distribute files to people that might not have eDonkey installed then this a perfect method for you. In the same directory as the content you want distributed also on eDonkey you simply create a small file that tells eDonkey how to get your content from the eDonkey network.

For example:
if you have a song rockout.mp3 available at www.yourwebsite.com/rockout.mp3 and you want to get the benefits of eDonkey if people happen to have it installed. You would create a file: www.yourwebsite.com/rockout.mp3.ed2k that is just the ed2k link to rockout.mp3.

This makes it very easy for people with a preexisting content site to drastically lower their bandwidth bill.

---

The ed2k link format

ed2k://|file|fileName|fileSize|fileHash|(optional params)|(optional params)|etc|

[optional params]
s=source
i.e.
s=http://www.overnet.com/files/overnet0.48.1.exe
s=bcp://68.49.48.183:3662|

It is helpful to include the partHashes if the file is not yet available on eDonkey
p=partHash1:partHash2:partHash3 ...
i.e.
p=8155f282201d5572a03577d642c7afc2:803815332e36c49aee5756bd44ad7edb

f=ed2k file
if the link is too long, clicking it in a browser will do nothing (around 2k), if the info is too long (too many sources, part hashes, etc whatever),
put the contents of the entire ed2k link in a file, and have f= point to it
i.e.
f=http://www.overnet.com/files/aVeryBigEd2kLink.ed2k

Complete examples:

1 http source with part hash information
ed2k://|file|mozilla-win32-1.4-installer.exe| 12263120| 5fe6cb6c303c188d10d4910c51474e6b| s=http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.4/mozilla-win32-1.4-installer.exe| p=8155f282201d5572a03577d642c7afc2:803815332e36c49aee5756bd44ad7edb|

multiple http sources
ed2k://|file|debian-update-3.0r1-i386.iso| 144736256| a03b9f8c573a71e653e09f2096e72904| s=http://ftp.belnet.be/debian-cd/images/3.0_r1/i386/debian-update-3.0r1-i386.iso| s=http://ftp.matrix.net.br/pub/debian-cd/i386/debian-update-3.0r1-i386.iso| s=http://ftp.tiscali.be/debian-iso/woody/i386/debian-update-3.0r1-i386.iso| s=http://mirrors.usc.edu/pub/linux/distributions/debian-cd/i386/debian-update-3.0r1-i386.iso|

overnet source
ed2k://|file|OverNet%20v0.49.4%20Setup.exe|1270857| 9478ba18c515ab22c37b19fb980c11c7|s=bcp://68.49.48.183:3662| p=9478ba18c515ab22c37b19fb980c11c7|

Note:
Currently the only sources that work are bcp (overnet) and http. There is a plugin architecture where 3rd parties can develop different plugins to connect to other ways of getting files. The http protocol is limited to a certain subset of servers (they must allow the download of partial content, etc). If the URL you put in redirects, it must point to another http server, not an ftp or it will fail.