On Mon, 7 Oct 2002, Tim Woodcock wrote: > > Have you received any off-list replies to this query? There has been > > little traffic on the list since your posting, and am wondering if a > > solution is available. > > I am wondering if I offended the developers or something. =8-o
> It is a problem because looking up a locked domain in our profile, and a > locked domain registered through a different RSP returns the same reason. I brought up this issue back in August. The official reply was the following... "check_transfer - coming in the next release (Aug 20th-ish) will be an extension to the API to determine if a domain is sponsored by your RSP account or not (will be an attribute of GETDOMAIN and LISTDOMAINS - you'll need username/password). This will also (built into the client code, you can code around it yourself) prevent renewals via manage/renew.cgi for domains you're not the sponsoring RSP for *tada*" Unfortunately, this doesn't meet our needs. We need a way to tell if a domain is registered with us or with another RSP without having to provide the username/password. It seems check_transfer looks at the domain's lock status before checking if the gaining and losing RSP are the same entity. It doesn't make much sense for check_transfer to check if the domain is locked, if we're already the sponsoring RSP. It seems to me the most logical and straightforward way to solve this issue and provide the functionality we need, is simply to reverse the order of those checks. -- Alex Bulan <[EMAIL PROTECTED]> Technical Operations Manager Korax Inc.
