Raphaël Ouazana-Sustowski wrote:
Sorry if I'm completly misunderstanding, but would not it be more simple and user friendly if the attributes were directly returned to the user, like do many overlays ? Ideally this could be : member/cn: ando member/cn: Pierangelo Masarati member/uid: ando
But to be more LDAP-friendly, we could see something like: cn;member: ando cn;member: Pierangelo Masarati uid;member: ando
Or maybe I'm totally missing a point :)
Sort of: we need to group together multiple bits of information. trying to force all of them into the value of an attribute in a way that is not compatible with its syntax is little LDAP-ish. The correct way to extend LDAP operations is by means of controls. What I'm preparing will provide a modification of the search operation that allows aware clients to easily obtain the information they asked for already parsed in a structure. As usual, the purpose of this operation consists in moving some of the client's tasks towards the server. We're trying to do it in a way that is respectful of LDAP and generally useful.
p.
Ing. Pierangelo Masarati OpenLDAP Core Team
SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ----------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Fax: +39 0382 476497 Email: ando@sys-net.it -----------------------------------