Quote:
Originally posted by ChrisM
You maintain that adding (back into the product?) a feature that would allow LimeWire to automatically (i.e, without human intervention or supervision) periodically search for sources that were not found upon the application's launch, would increase the traffic flow, with the implication that this would be a bad thing for the Gnutella network, and, therefore, for its customers. Again, if LimeWire's technical experience in this area causes it to make a reasonable conclusion that implementing such a feature would truly result in a net loss of customer satisfaction, then, of course, it would be wise not to implement such a feature. |
I think we have come a long way during the past months. A year ago most queries were dropped before they could reach the larger part of the network because all ultrapeers were simply overloaded. Today and especially when LimeWire 4.2 is released, we will even have a little bandwidth to spare that we could use to handle requeries.
Before automatic requerying is re-introduced it will need a lot of fine-tuning so it doesn't damage the network. I don't know when such a feature is going to be implemented. Probably not in the upcoming 4.2 but possibly in 4.4. - I am using already a requerying-enabled version at home.
Quote:
| What is the overall goal here? Is it to minimize traffic, or is it to maximize customer satisfaction by encouraging as many people to be sharing files on the network as possible? |
The overall goal is that manual queries are never dropped because an ultrapeer is overloaded with requeries. - Trust me, if it were up to me, you would have automatic requeries in the next version - but since I don't work there, it remains up to the LimeWire developers (especially LW's CTO) to decide that.