On 8/6/10 10:45 AM, Kiran Ayyagari wrote:
On Fri, Aug 6, 2010 at 2:02 PM, Stefan Seelmann<seelm...@apache.org> wrote:
So we will have some potential issues with the LDAP API : as we now have a
schema Aware, we have to load the schema into a SchemaManager. Right now,
all the schema is stored into a subproject (shared/ldap-schema) as LDIF
files. When we try to initialize the schemaManager, we first extract the
LDIF to the disk.
This is *very* bad ! When one will try to embed the API (in tomcat for
instance), one will face serious issues as the file system might not be
writable.
I think that is more worse when one wants to use the API as a client.
IMO the usage of the API must be lightweight. If I startup my program
to just do a search I probably don't want that a schema is loaded at
all, because it is just too heavy. Can we have a DummySchemaManager
implementation, that just does no validation and normalization?
not really, we let schema manager use the in-memory LDIF loader
(JarLdifSchemaLoader) so
no files will be written to disk.
Ok, so we are fine.
However, we should have a mode where the SchemaManager is not even
loaded. Be it a flag would be good enough.
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
