ETORRENT is a bittorrent client written in Erlang. The focus is on robustness and scalability in number of torrents rather than in pure speed. ETORRENT is mostly meant for unattended operation, where one just specifies what files to download and gets a notification when they are.
ETORRENT was mostly conceived as an experiment in how easy it would be to write a bittorrent client in Erlang. The hypothesis is that the code will be cleaner and smaller than comparative bittorrent clients.
Note that the code is not yet battle scarred. It has not stood up to the testing of time and as such, it will fail - sometimes in nasty ways and maybe as a bad p2p citizen. Hence, you should put restraint in using it unless you are able to fix eventual problems. If you've noticed any bad behavior it is definitely a bug and should be reported as soon as possible so we can get it away.
Currently supported BEPs:
- BEP 03 - The BitTorrent Protocol Specification.
- BEP 04 - Known Number Allocations.
- BEP 12 - Multitracker Metadata Extension.
- BEP 23 - Tracker Returns Compact Peer Lists.
GETTING STARTED WITHOUT INSTALLING
- Check Makefile.config for the right configuration options
- edit the file 'priv/etorrent.config'. Use the example 'priv/etorrent.config.example' as a start.
- 'rebar get-deps' to get the dependencies needed by the code.
- 'rebar compile' to compile the code into the BEAM format.
- 'make run'
- drop a .torrent file in the watched dir and see what happens.
- call etorrent:help(). from the Erlang CLI to get a list of available commands.
- If you enabled the webui, you can try browsing to its location. By default the location is 'http://localhost:8080'.
GETTING STARTED WITH INSTALLING
- edit 'Makefile.config' to suit your liking.
- 'rebar compile'
- 'rebar generate'
- You should now have a standalone embedded node in the 'rel' directory.
Either mail them to email@example.com (We are currently lacking a mailing list) or use the issue tracker:
Reading material for hacking Etorrent:
Protocol specification - BEP0003: This is the original protocol specification, tracked into the BEP process. It is worth reading because it explains the general overview and the precision with which the original protocol was written down.
Bittorrent Enhancement Process - BEP0000 The BEP process is an official process for adding extensions on top of the BitTorrent protocol. It allows implementors to mix and match the extensions making sense for their client and it allows people to discuss extensions publicly in a forum. It also provisions for the deprecation of certain features in the long run as they prove to be of less value.
wiki.theory.org An alternative description of the protocol. This description is in general much more detailed than the BEP structure. It is worth a read because it acts somewhat as a historic remark and a side channel. Note that there are some commentary on these pages which can be disputed quite a lot.
; vim: filetype=none tw=76 expandtab