"Compatibility" might not have been the best word.
Essentially, the API is trying to present the *same* data in a more structured manner.
It's goal is also to be flexible enough to allow for easy extensibility.
Dan
Daniel Manley wrote:
> LC. I've only got the answer to one of your questions.
>
> Dan
>
> "L.C." wrote:
>
> > [....]
>
> > 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 ?
>
> In the current OpenSRS system, a get_domain_info for type nameservers would have
>returned a denormalized set of fqdn and ip keys, such as: fqdn1, ip1, fqdn3, ip3.
>The digit marked the relative ordering of each nameserver in the domain. Removal of
>nameservers from a domain leaves gaps in the numbering (effectively cutting the
>nameserver out, as opposed to squeezing it out). The sortorder key in the proposed
>API preserves these gaps for compatibility with existing systems.
>
> >
> >
> > [...]
> >
> > --
> > L.C.
> > Network Admin @ InfoStreet
> > (818) 776 8080 x213
