Hi list.
I've decided to jump in and integrate OpenSRS stuff into our environment.
Taking baby steps, I wanted to just whip up a test script that verifies I
can indeed connect to the server and speak it's language. Apparently, I
can't. :)
I'm hoping someone can lend some insight to the error I
>>(1) Provides a native Perl API that can be used as the basis for web,
command line, and web service versions of "clients".
I think the API should be 100% language neutral and be implemented as an
XML Web Service. Why force anyone to customize or write from scratch in
any particular language?
>
On Tue, 7 Oct 2003, John Keegan wrote:
> So yep, you are right. There is indeed an error code 7502 as of April in
> the RCL which can now be used to handle this type of situation. Now I
> just have to figure out if it is easier to "back-port" this into our
> customized client, or update the client
Igor,
> Did I miss something? Is there plan to change XML API?
No you didn't, the XML serialization and deserialization of data aka OPS
is still used for all of our product. The data structures for the domain
provisioning aka XCP remain unchanged, however new product lines like
email and certs
