In our organization, each person belongs to two organizational units at the
same
time. So if we change RDN for any person, we have to modify the RDNs in both
branches. But modrdn does not work fine as a changetype in ldif in our case.
Specifically say, I have the following lines for one
Peter Van der Beken [EMAIL PROTECTED] writes:
Hi Dan and Paul,
You should explain to me what your question about threadsafety is,
because I haven't followed the discussion really closely. The datasource
currently waits till the last entry is in before asserting every result
as a child
Matthew Thomas wrote:
Dan Mosedale wrote:
...
So I've been thinking about this a bit, and it's a little unclear to
me whether the typedown preferences should be per-identity, rather
than just per-account. The current UI prefs are confusing to me, in
that they don't permit multiple
Hannes,
The Netscape Dir 4.x has a UID uniqueness plugin that ensures that uid
is unique within a suffix. You can disable this if you really want to
but Netscape does not recommend it.
A better question to ask is *why* you want multiple uids within a
suffix?=
Ian
Hannes Wornig wrote:
Hi out
[EMAIL PROTECTED] (Csaba Borbola) writes:
Dan Mosedale wrote:
http://www.mozilla.org/mailnews/specs/proposals/LDAPAddressingPrefs.html
is an approximate description of what we came up with (unfortunately
couched in my rather terse note-taking style). We'd love to hear
feedback from
[EMAIL PROTECTED] (Csaba Borbola) writes:
Hi,
We will store all the LDAP preferences in prefs.js
That is cool. The only question now is, how? Do you want to use the URI
scheme to store, as suggested in the refactored code document ?
Dan Mosedale [EMAIL PROTECTED] writes:
Hence the need for a query interface which
is able to return an enumeration of cards
(or perhaps URIs) or notify the RDF datasource
Which RDF datasource do you mean?
The existing nsDirectoryDataSource defined
as
