On 8/2/10 8:27 PM, Kiran Ayyagari wrote:
On Mon, Aug 2, 2010 at 8:03 PM, Emmanuel Lecharny<[email protected]> wrote:
Hi guys,
as I'm slowly refactoring the data structure we use to manage
NamingContexts, I just realized that we may have a way to handle
encapsulated partitions...
One of the Graal we were chasing was the possibility to define encapsulated
partitions. Let me give you an example :
if we define dc=example,dc=org as a naming context, then we have to define a
dedicated partition (be it JDBM, LDIF, HBase, in-memory, SQL-based). That's
good, but if we want to define a sub-partition for, say
ou=apache,dc=example,dc=org, we currenty can't. That means this ou=apache...
thing will be stored in the same backend than the partition it's defined
into (dc=example,dc=org).
so this kind of partition won't be shown as a naming context anymore,
its base is always dc=example,dc=org from a user POV, is that right?
It will be a NamingContext, and will appear as so in the rootDSE.
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
