Cs,
Totally agree with your protocol comments. We are using XML over
HTTPS and not perl.
In response to your question of "What else do you need?" I NEED (and
reading other posts, so do others) a well defined and clear XML
schema. Here is an example of part of the returned XML data structure
after being deserialized.
OPSRESPONSE.OPS_ENVELOPE.BODY.DATA_BLOCK.DT_ASSOC.ITEM3.DT_ASSOC.ITEM.DT_ARRAY.ITEM.DT_ASSOC.ITEM9.DT_ASSOC.ITEM13.DT_ARRAY.CHILD_LIST
I challenge anyone to work with this and quickly/efficiently:
Parse
Validate
Error trap
Process the action
Brad Thompson
Fagyal Csongor wrote:
Brad,
Tucows....
What's the issue here with providing and open XML standard that will
work with (.net, java, perl, Cold Fusion, asp, php, the list goes
on...) any client language?
I (and it appears others) just don't understand why you are sticking
with the outdated perl structures.
As a minimum, write some middleware code between the rest of the world
and your backend systems.
I have been voicing the same opinion for like years, proposing OpenSRS
to place a SOAP gateway (or something similar) "above" the current API.
However, some time (a year, maybe?) ago an HTTPS interface was put in
place. Now you can just create your XML structures and post those using
some standard HTTPS library. IMHO this is no better or worse than than
using SOAP, XML-RPC or (your favourite transport protocol here). In any
program you start up creating a "registration message" anyways (say, in
Java your would create an object which would serialize itself into
XML). And this method is platform independent, you do not need to use
Perl. What else do you need?
Actually I am still using Perl, but with libwww and Template.pm, and it
turns out to be much better (and flexible) than the CGI-s supplied by
OpenSRS.
- Cs.
|
<<inline: email_logo.jpg>>
_______________________________________________
domains-dev mailing list
[email protected]
http://discuss.tucows.com/mailman/listinfo/domains-dev
