Differences between version 16 and previous revision of BitTorrent.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
Newer page: | version 16 | Last edited on Saturday, July 23, 2005 1:36:21 pm | by AristotlePagaltzis | Revert |
Older page: | version 15 | Last edited on Monday, June 20, 2005 9:32:12 am | by AristotlePagaltzis | Revert |
@@ -1,14 +1,13 @@
-A PeerToPeer file downloading system written in [Python] (but with easy-to-use installers for a number of platforms, including [Windows]). Unlike most PeerToPeer systems, BitTorrent
works per-file. Users first download a tiny <tt>.torrent</tt> file which provides meta-data
on the download, including the [URL] of a centralised ''tracker'' that listens to special queries over an ordinary [HTTP] connection. The tracker itself does not have the file, it only keeps track of peers currently downloading the file to allow them to discover each other. The peers fetch sections of the file from each other in random order using a tit-for-tat system. The end result is a generally very efficient downloading system, offering insanely fast downloads even when the original provider of the file is on a very slow link.
+A PeerToPeer file downloading system which
works per-file, unlike most others
. Users first download a tiny <tt>.torrent</tt> file which provides MetaData
on the download, including the [URL] of a centralised ''tracker'' that listens to special queries over an ordinary [HTTP] connection. The tracker itself does not have the file, it only keeps track of peers currently downloading the file to allow them to discover each other. The peers fetch sections of the file from each other in random order using a tit-for-tat system. The end result is a generally very efficient downloading system, offering insanely fast downloads even when the original provider of the file is on a very slow link.
To make the system work, a client which already has the full file, referred to as the seeder, must initially connect to the tracker. This client is in no way special and its continued presence is not required either. There needn't even be a single client which has the full file at any given time, provided that all sections of the file exist on at least one of the peers signed onto the tracker.
-[BitTornado | http://bittornado.com/] is a BitTorrent client written in [Python], using [wxWidgets] for its [GUI], but
also offering a [Curses] interface. [Debian] users can <tt>apt-get install bittornado</tt>.
+! See
also:
-[Azureus
| http://azureus
.sourceforge
.net
/] is a BitTorrent
client written in [Java
].
-
-See also:
-* [BitTorrent homepage
|http://bitconjurer
.org
/BitTorrent/]
-* [Btorrents forum|http://www.btorrents.com/]
-* [Spanish BitTorrent FAQ|http://www.ayudabittorrent.com/]
-* [more bittorrent-
links|http://members.chello.nl/p.wiersema/index.html]
+*
[BitTorrent homepage
| http://www
.bittorrent
.org
/], including the official
client,
written in [Python
], with a [GTK] and a [Curses] interface
+* [BitTornado
| http://bittornado
.com
/], a
BitTorrent [Fork], currently using the old [wxWidgets] and [Curses] interface
+* [Azureus | http:
//azureus.sourceforge.net/], a client written in [Java
]
+* [Btorrents forum | http://www.btorrents.com/]
+* [Spanish BitTorrent FAQ | http://www.ayudabittorrent.com/]
+* [More BitTorrent
links | http://members.chello.nl/p.wiersema/index.html]
* FirewallingPeerToPeer