On Fri, Aug 6, 2010 at 12:20 PM, Kiran Ayyagari <kayyag...@apache.org>wrote:
> On Fri, Aug 6, 2010 at 2:49 PM, Emmanuel Lecharny <elecha...@gmail.com> > wrote: > > 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. > by default the SchemaManager won't be initialized, user has to explicitly > call > connection.loadSchema(), till then the API will not be schema-aware. > > This is where we can have an API flag to control whether or not the schema is loaded. This works out just perfectly. -- Alex Karasulu My Blog :: http://www.jroller.com/akarasulu/ Apache Directory Server :: http://directory.apache.org Apache MINA :: http://mina.apache.org To set up a meeting with me: http://tungle.me/AlexKarasulu
