Hi list (and especially Christian), I'd like to revive quite and old thread:
On Sunday 04 March 2007 22:06, Christian Biere wrote: > Haxe wrote: ... > > I would personally prefer the following behaviour: > > Directly after a completed download, if the user doesn't touch > > anything, the file keeps being served and advertised forever, but > > only through the mesh, not through any searches (this resembles > > bittorrent). Then, as soon as I manually hit the "clear from > > download list" button (or touch the file), the file becomes a > > "local" file and is treated as such, i.e. it is only shared if it > > is in a shared folder, but is then also advertised through search > > queries. > > One disadvantage of this is that files may exist in the mesh only. So > there might be thousands of sources but only a very few sharing them > making it hard or impossible to find these. That should be especially > true for new files which might only be available from a single peer > initially. Gtkg's current behavour is to stop sharing a file altogether as soon as its download finishes. When the download is complete, suddenly all peers in my active uploads list get a mere "not found". This is obviously even less helpful than to serve the file but to only advertise it through the mesh. The real problem here is that the downloaded file is stopped being shared even though I manually added my "completed downloads" folder to the list of shared folders (and also set the filename extension filter accordingly). To start sharing the new file after being downloaded, I have to manually hit "re-scan shared folders". Even worse, gtk-gnutella forgets the SHA-1 of the file it just checked, so everyone has to wait a long time until the file is actually shared. I absolutely understand that it might be not desirable to automatically re-share a downloaded file by default. But when I manually choose so by explicitly sharing my "completed" folder, it should be possible. That said, I am well aware that just sharing my "completed" folder is not the same as what I proposed before, because then the file would also be advertised through keyword searches. So why not keep sharing a just-downloaded file (while only advertising it through the mesh), given that sharing of partial files is enabled? What is the fundamental difference between the moment 1 sencond before and 1 second after the download finished that sensibly justifies to suddenly stop sharing it? Manual user interaction (like hitting "clear from list" would make much more of a difference, IMHO. bye, Hauke Hachmann ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Gtk-gnutella-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
