I recommend SOAP, given that is where the standards are going. SOAP supports
more complex data types (such as XML Documents), wheras XML-RPC only supports
simple data types.
I use Microsoft .NET platform and the C# programming language.
I think you will gain significant user base given the simplicity of using SOAP
APIs from many programming languages other than Perl.
Adam
----- Original Message -----
From: "Alan Hutchison" <ahutchison@tucows.com>
To: <discuss-list@opensrs.org>
Sent: Wednesday, May 28, 2003 7:35 AM
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: owner-discuss-list@opensrs.org
[mailto:owner-discuss-list@opensrs.org]On Behalf Of Adam Selene
Sent: Tuesday, May 27, 2003 4:46 PM
To: dev-list@opensrs.net; discuss-list@opensrs.org
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 archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:37:42 EDT