Re: Using the DHT to find download sources
"pwang708" <[email protected]>
| Newsgroups | gmane.network.gnutella.devel |
|---|---|
| Message-ID | <[email protected]> |
--- In [email protected], Raphael_Manfredi@... wrote: > > Quoting pwang708 <wang.peng@...> from ml.gnutella.dev-forum: > :Usage of the DHT: > :3) serving as distributed tracker for bittorrent enabled clients. A > :DHT can also be used to search torrent files. > > I vote against this for a Gnutella-oriented DHT. If you want to use > bittorrent, you know where to find it. > > If you want to search for torrent files in Gnutella, fine. A torrent file > is just another piece of information that can be shared. But if you want to > add to the DHT design things that are bittorrent-specific, then my answer > is no!. If you want to add that as private extensions for LimeWire, I > don't care as long as gtk-gnutella and any other servent joining the DHT can > operate correctly without these private extensions. > > :Requirements: I guess we come back to the question we argued before: do we want to improve users experience or we want to make Gnutella pure. I think installing less softwares is good to users. > :6) A richer API. The DHT can be used for several things which may have > :different requirements. > > Let's keep the DHT simple and focused on Gnutella. We're not trying > to design a super flexible generic DHT here. We're designing something > that can store IP:port vectors in limited quantities for any given key. > > Let's do this first. There are already many problems to solve to achieve > this efficiently. > Once implemented, it will not be easy to convince people to change. :-( The effort of listing requirements etc is trying to foresee as much as possible. So that, hopefully, we could have a similar view of the near future, next version DHT... We don't have to implement everything now. But we want to have a good design which is flexible to accommodate future changes, right? Best, Peng