Quoting Thomas Schuerger <[EMAIL PROTECTED]> from ml.softs.gtk-gnutella.devel: :Thanks for the explaination, Raphael. I think it's a useful feature. :What's not so useful is that this seems to be persistent. Wouldn't it :be good if this "induced" stopped-state was not written to the :searches.xml file? It doesn't really make sense to still stop these :kinds of searches when you quit GtkG and start it later (that was what :confused me in the first place). Perhaps this would require :distinction between automatically stopped searches and manually :stopped searches.
Well, it's also because it is persistent that the feature is "good", I think. Of course, we may think of "good" as different things, but consider this: a popular search (giving many hits) will still be a popular one when you stop and restart. The aim is to prevent broad searches that return many hits to be resent again and again on the network, and also makes sure that the searches you open are indeed useful for you (i.e. that you consume the hits that come back). In short, the purpose is to require human intervention to re-enable a popular search. This is the best compromise I could find. If you want me to not make that persistent, I will, but then there will be no auto-requery and you will have to close the search and open a new one to have a new query sent. That's what the GDF wants us to do. Is that what you want as well? I don't... Raphael ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Gtk-gnutella-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
