On Wed, 11 Jun 2008, Andrew Ziem wrote:
I wonder if there is a possibility to just get with rsync or over rss the
actual official torrents. So if there over night a update my server if self
is switching the torrents and dl+seeding the new one.
As Example RSS:
http://.../feed.rss?version=current&localisation=de&platform=Linux*
This possibility would make the distribution of a new torrent and active
seeding server a lot faster. Lets say they check every 15 minutes for
updates on the rss feed a new torrent would be deployed in max 1 h on the
seeding servers(100mbit/s). Ok.. If there 20 new torrents on 1 Server who is
seeding all of them it will take longer. That case could be solved with some
Seeding server who download the file from the mirror and afterwards seeding
it to the torrent.
You just want torrents over RSS? They are here
RSS: http://borft.student.utwente.nl/~mike/oo/bt.rss
Source: http://distribution.openoffice.org/p2p/
Sorry, I don't understand your whole email. I don't see any benefit to
adding rsync to this system.
I think Florian wanted to automate the process of checking for new
.torrent files, retrieving it, and starting the download + seeding process
automatically. Your RSS feed should fit that need handily, although it
may not handle stopping (if that's ever needed).
What I think might improve things a bit is, as I alluded to in an email
a few years back, to take advantage of typical bittorrent client behaviour
and the storage already used by the ftp/http mirrors which currently
synchronise using the rsync protocol. If I'm not mistaken, bittorrent
clients typically have a mode where they monitor a specific directory for
new .torrent files - they will automatically start when the .torrent is
created, and stop when the .torrent is removed. If the directory
structure via rsync for ftp/http mirrors could be rearranged such that
- .torrent files are placed in a directory, which the bittorent client can
monitor
- content can be structured in such a way that the bittorrent client can
reuse the same files that was already downloaded via rsync (or
alternatively, use bittorrent to download the files instead of rsync)
then it may be possible to have a situation where the mirror can serve the
content via ftp, http, bittorrent from the same storage (without needing
to duplicate it) and without needing administrative action to
download/upload .torrents or start/stop torrents.
Of course, with storage becoming cheaper, maybe this is too much effort
for too little returns. And I've not actually looked into whether content
actually can be structured in the suggested manner, using relative
symlinks or otherwise.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
