One thing we definitely need is error class information, i.e. permanent or
transient. This is important especially for domain registrations since we
need to know if we should queue the request and retry it later or mark it
as failed immediately. For example, socket errors are transient.
Another one, not API-related but still worth mentioning is the ability to
use the same method for transferring domains from other registrars as well
as OpenSRS. From what I know the OpenSRS domains are "non-transferrable".
I liked the change to using refs instead of copying entire hashes.
I would also love for a reseller to be able to register domains on user's
behalf without needing to know its password (once they already have one
domain registered). The reseller is currently seriously underpowered. It
has to be able to periodically check domains to see if they still point
to our nameservers, or the technical contact is us, etc. That is possible
by resolving the NS records or doing whois. It should be possible via the
openSRS interface as well.
About nameserver specification, since the list of nameservers is an array
is it really a need for the "sortorder" field ? What does the order in the
array mean then ?
The action and object fields in the reply are not very intuitive considering
the like-named items in the request data seem to have different meanings
( request: action="get", object="domain"; reply: action="REPLY", object="GET",
let alone the case).
--
L.C.
Network Admin @ InfoStreet
(818) 776 8080 x213
