Sebastian Kiesel wrote: >> For tracker based p2p applications, some guys proposed to embed the ALTO >> client within the tracker, so that the p2p clients do not have to be >> changed. > > It is a good question wheter it is more practical to change only the > tracker or all the peers in order to deploy ALTO. > However, I think this is not the most important question when we > ask ourselves where to place the ALTO client! > > I believe it is more important that we ask: Which configuration will > yield better results for the peer selection? Please read section > 2.1 of draft-kiesel-alto-3pdisc-02, there we explain why we believe the > ALTO client in the tracker will give better results as opposed to > putting the ALTO client in the peers. If you have questions or another > point of view pleas let us know, we'd be happy to discuss!
I don't have a strong opinion whether it will be better to have the client embedded in the peers or in the tracker, but I see good points on both sides. To add some information to the discussion, I've uploaded at the following link some charts showing the observed number of peers a BitTorrent client got to know while downloading a particular file in swarms of different size: http://ubiq.tilab.com/~enrico/graphs/ While the peers returned by the tracker -- the initial rise in the graphs -- are important in the first phase of the download, the number of peers discovered during the entire download period gets often very close to the size of the swarm. -- Ciao, Enrico
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
