Pierangelo Masarati wrote:
so it's pretty much unfriendly: consumer info is now in a child of the global overlay and nothing about that appears any longer in the database; I'd really love to have the global "consumer" overlay append its children below the appropriate database, but I don't know how to do it (I don't think it's possible within the current framework, because when the global overlay is processed the database entries do not exist; but I'd love to be contradicted).
I'm missing something, why does the consumer need to be a global overlay? -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc OpenLDAP Core Team http://www.openldap.org/project/
