Difference between revisions of "stoney core: Resellers Resource Mapping (REST - LDAP)"
From stoney cloud
| [unchecked revision] | [unchecked revision] |
(→Reseller creation (POST)) |
(→Overview) |
||
| Line 1: | Line 1: | ||
= Overview = | = Overview = | ||
The resellers resource mapping describes the business logic behind the LDAP to JSON transformation and visa versa for the request and response objects. The actual resellers resource REST API is located in the [[:Category:REST API|REST API]] category and is named [[stoney core: Resellers Resource - REST API]]. | The resellers resource mapping describes the business logic behind the LDAP to JSON transformation and visa versa for the request and response objects. The actual resellers resource REST API is located in the [[:Category:REST API|REST API]] category and is named [[stoney core: Resellers Resource - REST API]]. | ||
| + | |||
| + | Principles: | ||
| + | * for the ressource objects there is most of the time a one-to-one mapping between LDAP attributes and JSON object | ||
| + | * for collections only a subset of the ressource object attributes will be returned which may be also be merged or otherwise mangled | ||
= Resellers Resource Mapping = | = Resellers Resource Mapping = | ||
Revision as of 17:35, 3 January 2014
Contents
Overview
The resellers resource mapping describes the business logic behind the LDAP to JSON transformation and visa versa for the request and response objects. The actual resellers resource REST API is located in the REST API category and is named stoney core: Resellers Resource - REST API.
Principles:
- for the ressource objects there is most of the time a one-to-one mapping between LDAP attributes and JSON object
- for collections only a subset of the ressource object attributes will be returned which may be also be merged or otherwise mangled
