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.
_______________________________________________ domains-dev mailing list [email protected] http://discuss.tucows.com/mailman/listinfo/domains-dev
