batch.opensrs.net is identical to the normal server farm; the only
difference is it's isolated from the pool, and you're allowed to run
scripts against it. This system may have been under heavy load when you
attempted your script, I'll look into it...
And yes, this is the right list for more technical questions.
Charles Daminato
TUCOWS Product Manager
[EMAIL PROTECTED]
On Sun, 2 Dec 2001, Tom Brown wrote:
>
> What's the difference between the batch.opensrs.net server and the normal
> one? I thought I'd be nice and bash on it for half dozen or so lookups we
> do 4 times a day... but it's choking on me...
>
> DomainWatch::OpenSRS=HASH(0x84b7588)opensrs lookup on 'davidmeservy.com' failed:
> $VAR1 = {
> 'response_code' => 'OPS_ERR',
> 'response_text' => 'OPS Decode Error: Envelope Protocol Not Supported',
> 'is_success' => '0',
> 'attributes' => {
> 'reason' => undef,
> 'status' => undef,
> 'price_status' => undef,
> 'upg_to_subdomain' => undef
> }
> };
>
> The same code was working until I changed $OPENSRS{REMOTE_HOST}
> to be "batch.opensrs.net" ... this was just a simple availability
> check e.g.:
>
> my $lookup_request = {
> action => "lookup",
> object => "domain",
> attributes => {
> domain => $domain,
> }
> };
>
> my $lookup_results = $opensrs_xml_client->send_cmd( $lookup_request );
>
> Or are we simply supposed to use batch.opensrs.net to repeatedly
> send "register this domain" requests??? :-)
>
> p.s. Is this the right list? It is a code question, but not client code
> development. The discuss list doesn't seem very technical :-)
>
> -Tom
>
>
>
