-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello Roland,
It seem that we are always stuck on the same problem 1st the LDAP schema defination now the LDAP write function.
I'm asking are we doing the same thing? :)
please contact me ICQ: 601356 AIM: godinheavenchan yahoo: dcmwai SMS: +6019-2242326
Anything more :)
Roland Felnhofer �0: | Hi Markus, | | there is already a bug files in Bugzilla to deal with that. | (http://bugzilla.mozilla.org/show_bug.cgi?id=86405). Nonetheless nobody | had time to deal with it so far. | | Most issues someone could bring up with complex directory structures, | especially in the corporate environment could be solves in a first step | very pragmatically: | | complex DIT design: either you can "navigate" to the appropriate | location by using attributes you have in Mozilla anyhow or you have to | specify the destination DN explicitly. Or when worse comes to worse have | an individual entry for each sub-container, like you can have multiple | individual address books.
I didn't know that all people is worry about this complex DIT design, from my point of view. Once you have get the correct basedn work right, that didn't mather any more. As we all know that problem is now on the LDAP server and not the client, we are just to perform write command to the LDAP server. Who care if there have to be complex DIT, the basedn already told us where to write, what to be worry is did you have the right to write that LDAP addressbook :)
Unless you are talking about reading and writing on 2 different basedn then, it may make things a bit complex but it still can be done. Otherwise... Make one AB for read and one AB for write.
| schema: not a big deal - either your directory supports the whole
| Mozilla schema then you can have all attributes; if not - only these
| which are supported.
|
| Different access (write) rights to attributes and objects: Multiple
| solutions - Return an error message which fields can not be submitted to
| the server.
| Write/Update each attribute individually so you only get an error
| message for those fields you can't update/add.
| Let the user decide which of the above solutions should be used by
| having a pref (for example
| user_pref("ldap_2.servers.servername.bulkupdate", true); )
|Agree.
| Overall keep it simple and specific for the purposes it was designed. It | should be a LDAP Addressbook editor for Mozilla and not a multipurpose | LDAP editor allowing you to edit all kinds of LDAP attributes. | If you want a generic one, there is an quite good, java-based editor | available under: http://www-unix.mcs.anl.gov/~gawor/ldap/ | | Cheers | Roland
Yes, we are making an LDAP addressbook not a complex LDAP browser, if you still think that objectclass and some attribue (that is same for all contact) then Just add one more custome files. to define the needed value like a ldif files and write to the contact when ever change or create.
for e.g I would like then on my object class by having another files with following value (can be customize)
Objectclass: Rolodapcontacts Objectcalss: Pofix
and the LDAP Addressbook will write with these value when ever it touch the LDAP AB.
What do you think?
Thank You Chan Min Wai -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAj5h8eYACgkQV0p9slMZLW4ChwCfTIuxWinfhPJA9jWfLY4wzaqc PeAAoNfegTAeFOfa8ljUH9eiCzGOxfj/ =qb7x -----END PGP SIGNATURE-----
