On Fri, May 21, 2010 at 08:48:42AM +0800, Song Haibin 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! > But one additional thought comes into mind, peers usually exchange > peer list among themselves, does a peer also have to implement ALTO client > to select peers from these candidates got from other peers? I am not sure about this. Probably it would be the best if there was an ALTO client in the tracker and in each peer. But maybe in some scenarios it would be sufficient to have an ALTO client in the tracker, in order to get a "good" list of initial neighbors. For the peers you learn from your neigbors it might be sufficient to assess them by doing measurements. If you are interested not only in performance improvements but also in reducing ISP's costs you probably need to always ask ALTO. Thanks, Sebastian _______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
