Pro Yearly is on sale from $80 to $50! »

ServerSchemaCoreAPI

415d71aaeaa22d9ecfef343bda1ebde1?s=47 riywo
October 09, 2012

 ServerSchemaCoreAPI

415d71aaeaa22d9ecfef343bda1ebde1?s=128

riywo

October 09, 2012
Tweet

Transcript

  1. Core Server API Tool A API for A Tool B

    API for B Tool C API for C ServerSchema { node: server1, ipaddress: 10.0.0.1, role: [ {...} ], status: active } GET /node/server1?fields=... Dividing { node: server1, role: [{...}] } { node: server1, ipaddress: 10.0.0.1 } { node: server1, status: active } GET /node/server1 Validation Common Schema
  2. Core Server API Dividing Validation Tool C API for C

    Tool B API for B Tool A API for A ServerSchema POST /node { node: server2, ipaddress: 10.0.0.2, role: [ {...} ], status: active } POST /node { node: server2, role: [{...}] } POST /node { node: server2, ipaddress: 10.0.0.2 } POST /node { node: server2, status: active } Common Schema
  3. Core Server API Dividing Set Opetation Tool C API for

    C Tool A API for A ServerSchema [ server1, server2,... ] GET /node/search?fields=... &q=role=... [ server2,... ] [ server1,... ] GET /node/search?q= status=active or role=... GET /node/search?fields=... &q=status=active Common Schema Tool B API for B