I would like to see the transport problem discussed as well. I believe
most people would actually be able to implement the API reasonably well
were it not for the difficulties of setting up the encrypted channel.
Changing the API to use standard XML-based protocols is a good step forward but only takes us so far.
I had suggested a while ago to have SSL replace the initial connection setup (reseller authentication and encrypted transport setup). SSL supports both client and server authentication, and is already available for most languages.
By replacing the reseller key with a client certificate using SSL-TLS the API can be implemented completely at the application level which is arguably a much cleaner thing to do anyway.
Now, as far as the SOAP vs. XML-RPC vs EPP debate... I would prefer a generic XML-based API instead of a specialized one. The reason is that
way you can always add unrelated functionality you did not think about
(for example, email or certs management, etc). Also, one is more likely
to find resources on SOAP and XML-RPC than for EPP (encapsulating EPP over something else just compounds the problem).
Using the ole' google-meter for kicks (keywords need fine tuning but you get the idea)
SOAP XML 846,000 results XML-RPC 226,000 results EPP domain registration 3,300 results
-- L.C. (Laurentiu C. Badea)
I am cross-posting this email to Dev-List. See below.
Alan
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Alan Hutchison Sent: Wednesday, May 28, 2003 9:36 AM To: [EMAIL PROTECTED] Subject: RE: Feature Request: SOAP or XML-RPC API
I am interested in the level of interest in a SOAP or XML-RPC interface.
Some generic questions to solicit your input: SOAP or XML-RPC or something else - why? What are you trying to accomplish? Why does the current interface not meet all of your needs? How do you interface with us today API, RCL, RWI, scripts against RWI? What language(s) and operating system do you currently develop in?
Thanks in advance for your input.
Alan Hutchison Director, Product Management Tucows Inc.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Adam Selene 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
-- Regards, L.C. (Laurentiu Badea)
