" LATEST NEWS
||January 15, 2007 -- READ if you're interested in this project.
has been a project of mine for almost three years now. With
development starting February 2004, it was originally developed for
release and use by a specific torrent group, which is no longer active
to my knowledge. The source was put up here for a public CVS allowing
access to anyone else that thought it may be useful to them.
Times changed, I joined the US Army in late 2004, which basically
halted development as I was the sole developer. By the time I had a
computer again, and regular internet access, I had lost interest and
was too occupied by my other duties to continue development where I
left off. Now, I'm in Iraq, and have a portion of my day free for my
own use, which recently I've been using to work on this project again
to keep my mind active on something other than my day-to-day job, and
to keep my C skills from rusting away. I have no personal use for the
system I started building, so I need to know
SourceForge tells me I'm getting page views, whether by human or bot I
don't know, but someone is visiting. For those visitors to this page,
I ask you to read the description in the section below on what this
system does. Sound interesting? Have improvement ideas? Shoot me an
email via SF with your comments.
" ABOUT TORRENTWAVE
||The TorrentWave project
is a three-part BitTorrent tracking system. At the core is
the main backend, WaveCenter, which consolidates data from multiple
autonomous trackers into a databased resource accessible by authorized
clients. It provides a custom, extensible network API for the
administration and utilization of all resources.
from the core is a built from scratch tracker to allow for the data
transport, and administration that is at the core of the system.
WaveTrackers connected through the same TorrentWave server form a
network that allows the trackers to share global information, providing
a source of control for limiting leeching of
torrents on the trackers. Each tracker is designed specifically for
speed and scalability, two points where many popular trackers fail.
The tracker and main server share the same modular base code
allowing for rapid concurrent development.
The final piece is
the frontend. This can be
anything from a Perl CGI, to a PHP script, to an IRC bot. These
frontend clients have access to the database and administrative
functions through the network API.