[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LDAP replication requirements [virtual attributes]
-----BEGIN PGP SIGNED MESSAGE-----
I forget to mention something in the original message on virtual
attributes -- it is interesting to note that the problem only arises
with mult-master replication. With (e.g.) master-slave replication,
the slaves would be read-only, so the fact the virtual attributes
didn't update properly would never be noticed.
You example of nested groups is a good one, too: we need to do the
same thing, actually.
I didn't mean to say that total replication had to be implemented or
configured everywhere, only that the protocol had to support it, and
that admins had to be able to configure it and rely on it when needed
I do not believe that it is possible to enhance the schema to
represent virutal attributes, unless the enhancement includes a turing
complete programming language, because the computation of the virtual
attributes from the concrete ones can be totally arbitrary.
Paul J. Leach <paulle@xxxxxxxxxxxxx>
PGP Key ID: 0x978829DD
Fingerprint: 9EFA A405 39B4 F91F DE6F 8939 6FE9 F5D8
Key Servers: http://pgpkeys.mit.edu:11371 ldap://certserver.pgp.com
- -----Original Message-----
From: Uppili Srinivasan <USRINIVA@xxxxxxxxxxxxx>
To: ietf-ldup@xxxxxxx <ietf-ldup@xxxxxxx>
Date: Tuesday, April 28, 1998 2:51 PM
Subject: Re: LDAP replication requirements [virtual attributes]
>I would like to see this notion standardized. We refer to them as
>"dynamically evaluated attributes" or "computed operational
>Another example is the "leaf level members" of groups where the
>can be nested.
>But, I would think that "total replication" cannot be assumed. So
>if the semantics is supported on all nodes, these attributes are not
>guaranteed to compute to the same value.
>We should probably try to agree on a schema representation such that
>has no bearing on replication.
>Oracle Corporation |
>Box 659510 |Phone: (650)506-3039 Internet:
>500 Oracle Pkwy |Fax: (650)506-7122
>Redwood Shores |X.400: c=us; a=telemail; p=oracle; o=oragate;
>CA 94065 |
-----BEGIN PGP SIGNATURE-----
Version: PGP 5.5.5
-----END PGP SIGNATURE-----