Any chance of getting this feature implemented in the next release?
This will limit the number of connections the Project uses. Another way to limit connections is to use the right-click context menu in the Queue tab.
This limits connections per whole Project, not per a particular server, but since Projects load mostly one of the servers, this should work for you.
I know that you can limit connections for a project. However, it`s a pretty broad generalization to state that "Projects load mostly one of the servers." Personally I use OE for spidering the web, not for downloading individual websites. Therefore, limiting the number of connections for the project as a whole is of little value.
I notice in your Feature Comparison matrix that you listed "Server Overload Protection" as a feature, but you have "No" for all three versions of OE. Does this mean that you`re planning to add this feature soon? I`m considering purchasing the Enterprise Edition, but I`m pretty disturbed by the lack of this feature.
Is it really urgent and important for you to have this feature?
Well, I don`t want to throw off your whole development schedule, but the sooner the better :-)
Seriously though, I think this is a pretty important feature, not just for me, but for anyone who is doing any kind of web spidering. Many servers will ban your IP address if you make too many requests within a certain time period.
I`ve tried out a lot of different web spidering products and I feel that OE is the best one I`ve come across. However, paradoxically it`s also one of the few products that doesn`t support limiting connections by server.
We plan to release 3.5 version this week with the new command implemented there.
> We plan to release 3.5 version this week with the new command implemented there.
Thank you! That will be very helpful.