sabob wrote:
I've noticed a few sites does away with capcha's and instead ask
context related questions such as "What is the second word of the
third paragraph".
This is not acceptable for the customers :(.
The forms already ask too many questions, and the patience of the users is low (to the "leaving the page" level - judging by the stats with hidden javascript), so evey suplemental questions is not allowed :(.
sabob wrote:
> I believed that using Tread.sleep in Servlets (Click servlet in this case)
> is not reccomanded because
> unknown side effects - it's not always only one thread - sometimes are
> pooled, sometimes are more, if commet is used than on thread is delivering
> to more requests, etc.
Why not use a filter to slow things down?
Well, I haven't found a "smart" filter that does this (for PHP and Rails there are already ready to use solutions). Besides, to decide the probability if a request comes from a bot or not, some more data is required -> in Click is ready bound and easier to check, so I thought maybe there's a simple a way to do it
in Click, e.g. some trick in "onRender()" ?
sabob wrote:
You can also built checks which places a threshold on the amount
requests coming from specific IP addresses.
This makes sense only combined with a blacklist, since there are many proxies e.g. form companies, or even some providers with too few IP addresses. In these cases the "treshold" is quickly "consumed", and the users get very frustrated.
Since Click is addresed to commercial projects, it would be nice if there were some "read to use" solutions (or at least best practices) for such problems.
Thnx.
