Hi David,
Le 20 juil. 2004, � 13:31, David H. a �crit :
a) There is a vast amount of bittorrent clients b) There almost no bittorrent trackers.
You have to install yours.
|No, it's exactly the same as bitorrents files. Intensive CPU usage, very poor download speed and as soon as the upload has begun, the upload is shared from every downloader which has a chunck of that file.
| Other P2P systems (gnutella, Lopster aka OpenNap, mlnet, openFT) are
| much better at this. I'm not sure about their scriptability though--I
| guess the openFT interface protocol/libgiFT could be used to script it,
| and TekNap gives a scripty interface to OpenNap.
|
I do not really know enough about P2P to judge here, but does this not
mean one single person is once more sacrificing their upload to serve
the file?
No matter how wide spread the file might be, there is no
upload sharing, is that correct ?
Then, it's likely that those files would never seen or very difficult to reach for the same reasons Dave pointed.Well the bittorrent tracker would also be meant for people that want to share the debs they have created.
Please also note that I would onlyWill be very dangerous, since it's very easy to corrupt such files and/or exchange them during the sharing.
offer the tracker, and announce it, so that the Fink community can point
their clients to something like:
bt.finkmirrors.net:6969/announce , the rest is up to them. Since all the
files served over that "network" are not official, there is no need for
us to already think about signing. Even though that is high on my list
and as soon as we have a more recent apt, that will become a possibility
with the new deb signing tools floating around.
Mich�le <http://micmacfr.homeunix.org>
PGP.sig
Description: =?ISO-8859-1?Q?Ceci_est_une_signature_=E9lectronique_PGP?=
