Sounds like you just have to define exactly what you want to ban (e.g. automated access to your profiles at a rate of 2 per second) and then code something to prevent it or alert you to it.
I can't imagine that there is any widely-used solution to something like this. Perhaps you should start logging your users' actions with triggers that send emails to the administrators when limits are exceeded.
Denis Avdic wrote:
What our site is basically about is that people can access some information retrieved from a database. This person registered and basically went and accessed all of the profiles stored on our server, sequentialy, using an automated process (2 per second). This was in violation of our acceptable use policy. My question is what do people use if something like this happens, or how do they handle any other intrusions on all other levels.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
