Closed ddworken closed 10 years ago
Out of curiosity, why was this option removed?
IMO, there is a need for this in addition to the concurrent requests parameter. When scanning small websites, constantly maintaining even a single connection to the server would be noticeable compared to the normal load on the website. This can be avoided by limiting it to one connection per 30 seconds, which would not be noticeable compared to the normal load on the website.
I had figured concurrent_requests would serve the same purpose but I think you're right in that it serves a purpose so I readded it.
Added rate limiting in the form of a -r or --rate flag to set the number of requests per minute (using http://doc.scrapy.org/en/latest/topics/settings.html#download-delay). Changed something.com to example.com to comply with RFC 2606 (http://tools.ietf.org/html/rfc2606#page-2).