anchor.diff:  
   #### Update Client Configuration
   
  -__endpoint:__ `POST /client/{client-id}/config` <br>
  -__request body:__ `{<conf-cat>: [<comp-conf>,<comp-conf>]}`<br>
  +__endpoint:__ `POST /client/{client-id}/config` +
  +__request body:__ `{<conf-cat>: [<comp-conf>,<comp-conf>]}` +
   __response body:__ the updated client configuration `{<conf-cat>: [<comp-conf>,<comp-conf>]}`
   
   The endpoint accepts an request body with the configuration. 
  
positive.code: 
  #### Retrieve Client Configuration
  
  __endpoint__: `GET config/{client-id}` <br>
  __response body__: the created client configuration `{<conf-cat>: [<comp-conf>,<comp-conf>]}`
  
  Retrieve the configuration for the client with the `{client-id}`. If no configuration is present a `404 Not Found` is returned
  
negative.code: 
  __base path:__ `/client`
  
  The configuration REST Services allow to manage clients and configurations via API calls.
  
  All endpoints use `application/json` as media type.
  
  #### Create/Update Client
  
  __endpoint:__ `POST /client` +
  __request body:__ `{"name":..., "description":..}` +
  __response body:__ the created/updated client configuration `{"id":..., "name":..., "description":..}`
  
  ```
  curl -X POST -H "content-type: application/json" "http://localhost:8080/client" -d '{"name":"client-42"}'
  
  ```
  
  IMPORTANT: The clients name has to match the pattern [a-z0-9-]+ (it is used also for posting messages)
  
  #### List Clients
  
  __endpoint:__ `GET /client` +
  __response body:__ a list of clients `[{"id":"1","name":"client_42","description","Some description"}]`
  
  
  