At 1/6/04 10:07 AM, Roger B.A. Klorese wrote:
>You really need to set a standard of acceptable use, then configure
>sufficient hardware to accomodate it.
Seconded.
Aside from the fact that it's GOOD to tell people what the limits are so
they know if they're doing anything wrong, the current "policy" explains
why the batch server is so damn unreliable. I try to follow the rules and
use it for my automated scripts, which are actually fairly lightweight
and used for perfectly normal business purposes (i.e., NOT domain name
speculation), and the batch server just simply doesn't work about 10% of
the time. The failure rate is so high that I actually had to add code to
my scripts to first test if the batch server is working, then fall back
to the main server when it's not -- if I were a little less dedicated, I
would have simply given up on the batch server a long time ago.
I didn't realize it had no formal rate limiting in place. I suspect many
of the problems are due to other resellers hammering the thing, screwing
up everyone else's access, until someone from OpenSRS notices and
disconnects the offender if they keep doing it.
You guys need a rate-limiting policy that's automatically enforced.
-- Robert L Mathews, Tiger Technologies http://www.tigertech.net/"I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question." -- Charles Babbage
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:37:53 EDT