Or, I'd like to see a Windows DLL that handles the security layer and transparently passes the current command set to the API server.
I think this would mimimize Tucows R&D as well as preserve their current docs etc. It also prevents them from having to support 2 seperate projects.
I'm glad to see other complaining about the PERL setup. So far evertime I've complained on this list the result has been that I have been flamed by various Linux / PERL / etc. lovers.
Like it or no it took me just a few minutes to interface to enom's API and dispite the help of other I *HAVE NOT* been able to get the Tucows security layer to work even though my code *PASSES* all industry standard test vectors!
Oh, and before I get flamed again, I really hate dealing with enom (and manually transfer the domains into my Tucows account) but I do have automated registration needs and will continue to use enom until Tucows provides native Windows API support.
On Tue, 27 May 2003 17:37:01 -0400 [EMAIL PROTECTED] wrote:
XML WEB SERVICE - oh yeah that would be nice.
I have been begging for months.
John W Roche eInfosystems.net
-----Original Message-----
From: Adam Selene [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2003 4:46 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Feature Request: SOAP or XML-RPC API
I can't imagine this hasn't been brought up before.
Exposing a SOAP (or XML-RPC) API to the OpenSRS registration system
would really bring things along into the current decade (as opposed to
the arcane Perl setup).
Seems like it would be a fairly simple project.
Adam
This mail was content checked for malicious code and viruses by
GFI MailSecurity. GFI MailSecurity provides email content checking,
exploit detection and anti-virus for Exchange & SMTP servers. Email [EMAIL PROTECTED] for more information.
