2014-02-12 Telephone Conference DEVROOM / stepping stone GmbH

From stoney cloud
Jump to: navigation, search

Transcript of the Telephone Conference between DEVROOM / stepping stone GmbH

Location Skype
Date Wednesday, the 12th of Feburary 2014
Time 11:30 until 12:00
Participants
  • Christian Wittkowski <christian.wittkowski@devroom.de>: CWI
  • Christian Affolter <christian.affolter@stepping-stone.ch>: CAF
  • Tiziano Müller <tiziano.mueller@stepping-stone.ch>: TMU
  • Michael Eichenberger <michael.eichenberger@stepping-stone.ch>: MEI (Transcript)
Non participants
  • Pat Kläy <pat.klaey@stepping-stone.ch>: PKL
  • David Vollmer <david.vollmer@stepping-stone.ch>: DVO
  • Pascal Jufer <pascal.jufer@stepping-stone.ch>: PJU
Agenda

Open Questions:

Transcript

No. Text What? Who? When?
1 In principal, the REST API should know the scope of variables. For example: billingAddress should be able to contain location. No location attribute is currently used, but it could be used in the future. Info All 2014-02-12
2 q and sort are Reserved Keywords and are therefore not allowed in the JSON payload. Info All 2014-02-12
3 The REST API defines the following line as a return value. This is required and will not change.

You are correct in the assumption, that the following line will return the same information:

Additional Information:

  • Filtering, sorting and searching allows for the above query.
  • Via proper routing both calls (urls) should end in the same controller without further manual programming, as the framework should be able to do this for you.
Info All 2014-02-12
4 We've updated the Relations section of the documentation. It should be simpler to implement this way. Info All 2014-02-12
5 No, currently you do not have this possibility. The following example will return all the entries and display the modifyTimestamp:
ldapsearch -v -H "ldaps://ldapm.stoney-cloud.org" \
              -b "ou=people,dc=stoney-cloud,dc=org" \
              -D "cn=Manager,dc=stoney-cloud,dc=org" \
              -s one "(objectClass=*)" \
              "modifyTimestamp" \
              -LLL -W

filter: (objectClass=*)
requesting: modifyTimestamp 
dn: uid=4000002,ou=people,dc=stoney-cloud,dc=org
modifyTimestamp: 20131220135513Z

To achieve server side sorting, we need to install the Server Side Sorting and Virtual List View Overlay:

How to set a LDAP control: http://search.cpan.org/~marschap/perl-ldap-0.58/

We'll define how to create the hash used as the ETag.

  • Use Case 1: Business object has a one to one relation in the LDAP directory.
  • Use Case 2: Business object has a one to N relation in the LDAP directory.

See Mandatory headers for example. The implementation details will be described on another page.

To Do MEI / TMU 2014-02-19