[db-wg] New minor release 1.71.1 to fix REST API JSON issue

On Thu, Feb 06, 2014 at 08:03:05PM +0100, Johan Åhlén wrote:

> We’re looking into this issue right now and will let you know as soon
> as we have a fix available.

Johan, one of your engineers reached out to me (thanks!) and it seems
that I was using a legacy endpoint 'apps.db.ripe.net' instead of the new
'rest.db.ripe.net' URL. 

Although it was communicated that apps.db.ripe.net would be deprecated,
starting with the 1.71 release, apps.db redirected to the new software,
which might work for the majority of cases, but not all and this is what
bit me. 

To all other readers: just stop using apps.db.ripe.net and expect two
changes:

    - 'whois-resources' is not the root of JSON API results
    - any 'object' under 'objects' is not a JSON object but a JSON array

RIPE DB ops:

    - it might be worth considering a versioning scheme for the schema
      which is communicated inside the JSON results like stat.ripe.net

Have a good night!

Kind regards,

Job


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 873 bytes
Desc: not available
URL: <https://lists.ripe.net/ripe/mail/archives/db-wg/attachments/20140206/d1e03046/attachment.sig>