> Charles, any chances of an API way to tell if we're the RSP for a domain?
> Maybe a new response attribute can be added to lookup, if changing
> check_transfer isn't practical.
Already talked about this internally (as a result of this
discussion). Changing the check_transfer isn't really practical
(it's not meant as a tool to determine if you're the sponsoring
reseller), but a new command - one that does not require a cookie
- will be in the works.
A note from our internal discussions:
<snip>
What you're doing isn't the intention of this command, any data
returned from it shouldn't be used in this way. There are a
couple of cases where this wouldn't return the information that
the reseller is wanting, in particular:
- reseller doesn't have access to the tld that they're checking
- tld that they're checking doesn't support transfers
(ie, .tv, .uk, .name)
Given that the information is not 100% and that this isn't the
purpose of the command, there's not much point in changing the
order of the operations IMO
</snip>
:)
Charles Daminato
TUCOWS Product Manager
[EMAIL PROTECTED]
On Tue, 8 Oct 2002 [EMAIL PROTECTED] wrote:
> Hi Paul,
>
> On Tue, 8 Oct 2002, Paul Chvostek wrote:
>
> > It's less elegant, but you couls use an sslbot-style approach. If
> > https://batch.opensrs.net/resellers/index?action=view_domain&name=example.com
> > does not contain "Unable to find domain" in the body, the domain is
> > probably yours.
>
> Yeah, that'll work... I could also maintain a local list of my domains and
> periodically sync it with the server. I'd like to avoid relying on this,
> though.
>
> Charles, any chances of an API way to tell if we're the RSP for a domain?
> Maybe a new response attribute can be added to lookup, if changing
> check_transfer isn't practical.
>
> --
> Alex Bulan <[EMAIL PROTECTED]>
> Technical Operations Manager
> Korax Inc.
>
>
