At 15:33 15-2-2001, you wrote:
I've made great progress in creating a Windows COM object that performs all
the functions documented in the OpenSRS Client.  As I enter the testing
phase, I am noticing problems that suggest that the documentation is
incomplete.

Can someone explain what additional information is need or the sequence of
functions to call in order to make a feature work as documented?

The following functions have been tested and work properly:
LookupDomain, SWRegisterDomain, GetDomainInfo, GetDomainList,
GetDomainNameServers, GetDomainContactInfo, GetUserInfo, AddSubUser,
GetSubUser, ModifySubUser, DeleteSubUser, QuitSession, SetCookie,
DeleteCookie, ChangePassword, ChangeOwnership.

The following functions return an error:
UpdateCookie - No Domain Supplied
CreateNameServer - Permission Denied
ModifyDomainAddNameServer - Command failed: unable to verify existence of
nameserver ns1.merchantware.com

Does anybody have a system with these functions working?  As a side note,
DomainDirect.com also seems to fail when creating a name server.

The latter 2 actions (ModifyDomainAddNameServer and CreateNameServer) do not work correctly in the test (horizon) enviroment. Or at least the ModifyDomainAddNameServer action does not unless you use the dns servers that are in the FAQ:

-
RSPs using the test environment can not register domain names through OpenSRS with many nameservers that otherwise exist "in the real world". This is a side-effect of the way that we have set up our test environment. The data set included in the RITE is minimal and does not include a comprehensive list of name servers.

The production ("live") environment does refer to this information.

While you are in the test environment, please feel free to use these nameservers:
ns1.domaindirect.com
ns2.domaindirect.com
-

I think the CreateNameServer is 'disabled' in the test enviroment for the same reason, although I'm not sure about that one. The UpdateCookie worked for me (..or I think, can't recall testing it in my php wrapper), the protocol specs say the following (this is from my php wrapper manual):

UpdateCookie
Purpose:
Allows the client to change the domain associated with the current cookie
Values: (str $cookie, str $new_domain)
$cookie - Current cookie.
$new_domain - New domain for cookie.

Reply via email to