1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On July 23, 2003 11:35 pm, bdharring wrote: |
5 |
|
6 |
> I realize this particular horse has been beaten well past it's death, |
7 |
> but why create a separate p2p system instead of using bit torrent? |
8 |
> Just curious, I'm aware of how bit torrent is structured, but that's |
9 |
> about it... |
10 |
|
11 |
Bittorrent is well suited to distrubuting a small number of large files, |
12 |
that is what it was designed for. The downside is you need a separate |
13 |
instance of bittorrent running for every file that you are shaing, so |
14 |
if you are sharing several hundred files you need several hundred |
15 |
copies of bittorrent running. |
16 |
|
17 |
Another problem is that in bittorrent the client side server and the |
18 |
fetcher is the same program, for our purposes we need a separate |
19 |
program to perform each function. |
20 |
|
21 |
> Other then that, you've mentioned that you're attempting a proof of |
22 |
> concept, care to elaborate on some of the aspects of the particular |
23 |
> p2p system you're attempting to create/test? |
24 |
> ~bdh |
25 |
|
26 |
Lets see: |
27 |
Central repository of hashes for security. |
28 |
Only authorized files will be shareable. |
29 |
Separate server and fetcher program. |
30 |
Will download simultaneously from multiple sources. |
31 |
Drop in replacement for wget via FETCHCOMMAND= |
32 |
Rate Limiting on the server (but not to 0). |
33 |
The fetcher will automatically start the server (to limit leaching) |
34 |
Will automatically share your distfiles directory |
35 |
??? |
36 |
|
37 |
It is NOT being designed as a general purpose p2p program. I have no |
38 |
desire to become a target of the MPAA or RIAA |
39 |
|
40 |
- -- |
41 |
Fred Van Andel |
42 |
fava@g.o |
43 |
GPG KeyID: 76526AD599455482 |
44 |
GPG fingerprint: 64E4 4BAB 9C99 D565 3E3C F5D0 7652 6AD5 9945 5482 |
45 |
-----BEGIN PGP SIGNATURE----- |
46 |
Version: GnuPG v1.2.2 (GNU/Linux) |
47 |
|
48 |
iD8DBQE/HjebdlJq1ZlFVIIRAmL4AKDWKGB+SEmMA/s9cdR6D15O/5sMvgCdE2aH |
49 |
ZMna7nBS7ESfa3uUnCY02/M= |
50 |
=/haH |
51 |
-----END PGP SIGNATURE----- |
52 |
|
53 |
|
54 |
-- |
55 |
gentoo-dev@g.o mailing list |