Paul & List Sorry for the confusion on this matter, perhaps its time to restate what's been posted in the past and define it a bit better.
The rule of thumb for batch.opensrs.net is as follows: There are no numerical rate limits as to how often or how many connections a reseller can make to the batch pool. However this system is monitored for performance as well all API rate limits are enforced in the same manner as the LIVE system at the application level. If an IP and its related process requests, causes the system to suffer performance issues that negatively affect all batch users, then the offending IP will be blocked for a period of 24 hours and automatically reinstated the next business day. I hope this helps in clarifying the issue. Let me know if you have any further questions. Thanks, James -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Chvostek Sent: Sunday, January 04, 2004 5:17 PM To: [EMAIL PROTECTED] Subject: Re: batch system access limits On Sun, Jan 04, 2004 at 03:00:31PM +0200, Sergei Kolodka wrote: > > PC> The only ways to find out what access limits exist are apparently > PC> to check my contract (which predates the existence of > PC> batch.opensrs.net, though I also see no mention of this matter in > PC> the contracts currently at resellers.tucows.com) or to contact my > PC> sales rep, who of course isn't available for escalation until Monday. > > Paul, take a look to discuss-list archives for Chuck D. answers about > batch.opensrs.net. Subjects were "AUP for batch.opensrs.net?" > and "Batch.opensrs.net". Yes, I too found Chuck's note of Jan 07 2002 - 19:36:33 EST: | a good rule of thumb is to stay below 5 commands per second (some of | our largest resellers, even at peak periods, would only send 1 or 2 | commands a second). But this is not a documented policy. As it was merely a list message almost two years ago, I thought it best to check. And as it turns out, Chuck's email is entirely at odds with what Oscar told me on the phone on Friday, that a cronjob running a GET on batch.opensrs.net once per minute would probably get me cut off without further notice. I strongly suspect (based on what he said and his follow-up reply on this list) that Oscar simply didn't know what he was talking about. Of course, if an AUP for batch.opensrs.net has not been developed, I don't expect him to make one up on the spot. Unfortunately, as far as I've been able to gather, he did in fact make one up on the spot. At this point, clarification is required from his superiors. In addition, this incident should be a cue to Tucows that their support staff either need better education, both in the way Tucows works and in how to deal with situations where they don't know the answer. Either that, or that the customers need to be informed as to the level of support that can be provided outside Eastern time business hours. And if the support provided is about as useful as no support at all, then perhaps Tucows could save a bit of money by reducing support hours. -- Paul Chvostek <[EMAIL PROTECTED]> it.canada http://www.it.ca/
