3 This is yet another Tech. Preview release. The torrent client works
4 to the point where it can be used to download things, but it have
5 not seen much testing yet and there are numerous places it can be
6 improved still. Yet, there are so many changes, that it warrants a
11 - There is a set of new commands for viewing what is currently
12 cooking in the torrent client. etorrent:l/0, etorrent:s/1,
13 etorrent:h/0. Implemented with help from Tuncer Ayaz.
15 - Changed build infrastructure. No more autoconf. It simplifies the
16 build structure considerably. Introduce the use of EMakefile for
17 building the erlang parts of the system. Reinstate all make targets
18 and add a 'tags' target for building a TAGS file.
20 - etorrent now correctly handles the 'min_interval' tracker response
21 parameter. It is not strictly part of the spec, but everybody uses
24 - Add support for installing etorrent. A shell-script, etorrentctl,
25 is provided to control the etorrent daemon.
27 - etorrent no longer pre-fills files it want to download with
28 junk. It uses the semantics of fseek() to make a file of the right
31 - several ETS restructurings has brought the memory use
32 down. Before, etorrent would take some 660 megabytes of memory
33 running 20 torrents. Now it is more like 50-80 megabytes for 20
34 torrents. More can be shaved but this is a good start.
36 - New choking/unchoking algorithm, based on a combination of
37 BitTornado/BitTorrent/Transmission. This is not the smartest one can
38 do, but it follows the spec more or less precisely.
40 - Event Publisher. A gen_event OTP behaviour one can subscribe to and
41 get information about the system. A logfile subscriber is there by
44 - Rate calculation optimizations. etorrent now uses a running
45 average over a period of up to 20 seconds to measure the rate of a
46 peer. This yields a more fair measurement of individual peers so we
47 claim the best peers. While here, change the sockets to be passive
48 for now. It bumps the CPU-usage, but makes the rate calculation more
51 - Robustize the supervisor tree. etorrent is now less likely to die
52 due to a crash somewhere in the tree. It is not entirely safe yet,
53 but it will be during the next releases.
57 First Techonology Preview.