Years ago, when I was in college, it used to be fun to walk into a room and say "x" is the best programming language and watch the resulting argument.Bad boy! :-)
That seems to have been replaced with "x" is the best standard for data interchange.Well, actually I am in favour of SOAP, and we use no Microsoft products whatsoever. We use Perl most of the simte. SOAP is W3C, so is XML. There are excellent bindings for Perl for these _standards_ - better than the home-grown solution the OpenSRS API uses.
.. and unlike the early days, when this list was dominated by the *nix/Perl fanatics, it now seems to all be SOAP, XML, .NET, whatever -- but very Microsoft.
Some of the argument seems to say that the Perl-style ciphers are impossible to implement.I did not find it that easy even to import the API into our mod_perl application. I do not even like the idea of importing _anything_, but standard CPAN modules.
If you search around, there are at least two native Win32 projects out there. One has produced a component that builds the XML, or you can just use it to manage the communications, the other published enough information about the encryption to give anyone implementing their own a good start.
.. and for others, the Perl client is good enough. It also shows that the existing technology is platform-neutral, or we'd be registering domains through the RWI.
Also in our application I tend to do things like
$ourapi->setLiveEnvironment;
Now the implementation of the setLiveEnvironment method does not look nice, because of the current API I have to use. All right, I can manage, but I would still prefer a more standard way. Or just take a look at OpenSRS.conf...
Just my two cents.
- Csongor
