Sean Dean wrote:
I actually keep my fetcher.threads.per.host value at the default 1, but have tried up to 3 without any noticeable errors strictly based on this setting. I guess this comes into play more if your fetching from many of the same hosts, in which you might want to cheat and raise the setting up a notch but in doing so you might see more http-related errors, as you have witnessed.
The default is 1 also because of netiquette - it's generally frowned upon by webmasters if someone uses more than 1 concurrent request, or makes requests too often (without any delay) - and quite often all requests from such sources get blocked at the firewall level - sometimes, even whole IP classes get blocked.
So, t(h)read carefully ... -- Best regards, Andrzej Bialecki <>< ___. ___ ___ ___ _ _ __________________________________ [__ || __|__/|__||\/| Information Retrieval, Semantic Web ___|||__|| \| || | Embedded Unix, System Integration http://www.sigram.com Contact: info at sigram dot com
