[EMAIL PROTECTED] schrieb:
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).
Thanks for your answer. I already know the rss feed and also the rsync
url. Your general idea about what i want is correct. I want nothing to
do if there is a new offical stable version of OOo on the torrents.
I also would like to see that torrent is faster in distributing to a lot
of server than rsync. :-D
Problem: I don't see a easy possibility for me to keep difference from a
devloper or an old torrent in the rss feed. The informations in the Java
Applet would be a nice thing if they where add also to the rss feed. In
this way it would be a lot easier to filter the torrent.
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
Well i did more think to use rsync to get the torrents with a filter (
--exclude=* --include=OOo_2.4.1_*.torrent ). But well as you see...
there is no way to filter the current out automatically without the
current version number.
The advantage is torrent is more like: Upload the file one time to a p2p
server seeding network and all server will have the file afterwards in
"short" time completed. I think this would work easy up to 100 server on
a closed tracker. But in the end you cant compare bittorrent to rsync
because of the different functions.
- .torrent files are placed in a directory, which the bittorent client
can monitor
btlaunchmanyheadless directory
- 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)
btdownloadheadless name.torrent --save_as=/path/to/file
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.
Well storage is cheap yeah in home use ^^ still server HD's are not that
cheap and i cant just add some more because they are only rent.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
