Do we need a new RequestScheduler?
I definitely figure out that the instability was related to the bandwidth limitation mechanism, but it was no fixed with my posted suggestion.
I prefer we have only a single fetcher implementation for now. Are there features missing that folks need? If so, let's add them, but let's try to avoid forking the fetcher again.
If someone believes that RequestScheduler is a better foundation for the fetcher, and they can submit and support a version of it that works with the new APIs, then we can remove Fetcher.java.
Cheers,
Doug
------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ Nutch-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nutch-developers
