Return-Path: Delivered-To: apmail-directory-api-archive@minotaur.apache.org Received: (qmail 76307 invoked from network); 6 Aug 2010 09:20:53 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 6 Aug 2010 09:20:53 -0000 Received: (qmail 30096 invoked by uid 500); 6 Aug 2010 09:20:53 -0000 Delivered-To: apmail-directory-api-archive@directory.apache.org Received: (qmail 30062 invoked by uid 500); 6 Aug 2010 09:20:52 -0000 Mailing-List: contact api-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: api@directory.apache.org Delivered-To: mailing list api@directory.apache.org Received: (qmail 30054 invoked by uid 99); 6 Aug 2010 09:20:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Aug 2010 09:20:52 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ayyagarikiran@gmail.com designates 209.85.161.50 as permitted sender) Received: from [209.85.161.50] (HELO mail-fx0-f50.google.com) (209.85.161.50) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Aug 2010 09:20:44 +0000 Received: by fxm9 with SMTP id 9so4934597fxm.37 for ; Fri, 06 Aug 2010 02:20:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; bh=ugPknnwerg9bVx7WcJ54Y3YJ8O8mPy4qZjx8hf0MR1o=; b=TEnOgdgNxZ2wRr9RsJfPjuYPSkeEC3u8FcaaCp39fcDAxIn0NyN1WvNK3OqnEehlDp itlrAw/O8IVhPWy6FnG/B2jvus8vwqTpIEWCkTjnAzhNEAfwGD/M2EVQ2OBtd4vyoUzN y6rNEZmNGTx535CpCEDRYoEA/UVfuq+KowBJE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=YPgUTXKuDaHAqtZEO4Q+Ex0PK3vZTUV8vpXCuZeEvXex9m5UHmejivzn49zC/7ZD00 jVUZtFIQ+vZN41tAb1v6FdgOfZ7xxAE7zd/qpZmBfrMvi2HMqGy7+mIBSbE4V14Hnbii kA0Ve+xPiKvPKpTxikiGsFP4letsdSD8KPUI8= MIME-Version: 1.0 Received: by 10.223.104.134 with SMTP id p6mr12479300fao.10.1281086423169; Fri, 06 Aug 2010 02:20:23 -0700 (PDT) Sender: ayyagarikiran@gmail.com Received: by 10.223.116.9 with HTTP; Fri, 6 Aug 2010 02:20:23 -0700 (PDT) In-Reply-To: <4C5BD39B.90309@gmail.com> References: <4C5AD7DE.6050002@gmail.com> <4C5BD39B.90309@gmail.com> Date: Fri, 6 Aug 2010 14:50:23 +0530 X-Google-Sender-Auth: NccVj1e4gOmoIkmCzZP3JlsaUlE Message-ID: Subject: Re: Some thoughts I had under my shower this morning... From: Kiran Ayyagari To: api@directory.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Fri, Aug 6, 2010 at 2:49 PM, Emmanuel Lecharny wro= te: > =A0On 8/6/10 10:45 AM, Kiran Ayyagari wrote: >> >> On Fri, Aug 6, 2010 at 2:02 PM, Stefan Seelmann >> =A0wrote: >>>> >>>> So we will have some potential issues with the LDAP API : as we now ha= ve >>>> 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 LDI= F >>>> files. When we try to initialize the schemaManager, we first extract t= he >>>> 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 b= e >>>> 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 c= all connection.loadSchema(), till then the API will not be schema-aware. Kiran Ayyagari