Brad,
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
You are right about that. This is more complex than it should be. I mean things like
GET https://opensrsandstuff.com/simple?username=foo&password=bar&domain=example.com&action="">
GET
https://opensrsandstuff.com/simple?username=foo&password=bar&order_id=123&action="">
are so much nicer. Maybe more difficult structures cannot be pushed through by simple url-encoding without some hacking, but still, you can always POST :-)
I challenge anyone to work with this and quickly/efficiently:
Parse
Validate
Error trap
Process the action
Well, or course this is more difficult than it could be. We had to write our own wrapper around it, too (basically flattening the whole structure). Using something DOM-like (we use XML::Simple actually) it is less than 100 lines, though. That is not THAT bad :-)

- Cs.
_______________________________________________
domains-dev mailing list
[email protected]
http://discuss.tucows.com/mailman/listinfo/domains-dev

Reply via email to