Paul,
I am just looking into developing a COM object for OpenSRS in ASP and would be very interested in testing your component or even working with you on this one.
Regards,
Stephen Smith
[[EMAIL PROTECTED]]
-----Original Message-----
From: Paul Rony [mailto:[EMAIL PROTECTED]]
Sent: 15 February 2001 14:33
To: '[EMAIL PROTECTED]'
Subject: OpenSRS Client for Windows/IIS ASP
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.
Feel free to contact me if you are interested in testing the OpenSRS Client
COM object for Windows/IIS.
Paul Rony
DomainSage
THE CONCEPT GROUP
Hexworthy House
Lawhitton
Launceston
Cornwall
PL15 9PE
Sales: 020 8943 0076
Office: 01566 776398
Web: www.c2100.com
==================================================================
This email message and information it contains may be priveleged
and/or confidential, and is for the use of the addressee only.
Unauthorised use, dissemination or copying is prohibited. If
you are in possession of this email and are not the addressee
please notify the sender immediately.
Although every effort has been made to ensure accuracy neither
Concept 2100 Ltd nor the author can accept liability for any
errors and omissions.
This message cannot be used as evidence of any agreement or
undertaking unless seperately confirmed by a fax.
==================================================================
