Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 83542 invoked from network); 2 Apr 2008 16:04:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Apr 2008 16:04:39 -0000 Received: (qmail 91698 invoked by uid 500); 2 Apr 2008 16:04:37 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 91663 invoked by uid 500); 2 Apr 2008 16:04:37 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 91652 invoked by uid 99); 2 Apr 2008 16:04:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Apr 2008 09:04:37 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of akarasulu@gmail.com designates 64.233.184.236 as permitted sender) Received: from [64.233.184.236] (HELO wr-out-0506.google.com) (64.233.184.236) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Apr 2008 16:03:56 +0000 Received: by wr-out-0506.google.com with SMTP id c48so1863966wra.1 for ; Wed, 02 Apr 2008 09:04:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth; bh=/5icw/Szo4qSq2OWir2HvLzpLKxQW3AtRCZoZC2hJFU=; b=BvNxjKwkoAIqL5LnkrDhX2T+UC4MQudSDKGjWdt6rhJ3KLqm7r4zlOVYEsV0cyfvjSx+UDGCrCaA7Tsb93GTm74B4ANPjDhsadQVra1g9oH46xHugNS/LJi3Fa5SeW2La1QGXfQ86VxTWCWs5K6lYuh0YL5IiHHUs9RE/QFEb0g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth; b=kAOrMPEEcYXwoKMYcRHgSuxWIFOMl4OlAijAXjmsp89Fkl1iQvOR94BXn6qL/XOFk+FowRgaBos2ab8rSRsi1ZVvXoDyIIuBOCEZO/t/dEJORd1nTYNAQ+Z0IE+K5MkgJhRjIhIh81SvhOS5I/eoSmLz37lvx4Ld8oiDuBPKI4o= Received: by 10.140.248.17 with SMTP id v17mr5108931rvh.9.1207152247241; Wed, 02 Apr 2008 09:04:07 -0700 (PDT) Received: by 10.141.113.13 with HTTP; Wed, 2 Apr 2008 09:04:07 -0700 (PDT) Message-ID: Date: Wed, 2 Apr 2008 12:04:07 -0400 From: "Alex Karasulu" Sender: akarasulu@gmail.com To: "Apache Directory Developers List" Subject: [Studio] Using JDBM for secondary cache MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2067_16671136.1207152247244" X-Google-Sender-Auth: ebffa9db88d98247 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_2067_16671136.1207152247244 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Stefan S., Do we use a secondary cache for Studio? Just wondering because of the performance issues someone noted on the user list when dealing with a very large directory. The idea occurred to me that the JDBM code for JdbmTable and JdbmIndex could potentially be used by Studio to help solve some of the caching problems. If this is something you think will help we can move this code into shared so both the server and Studio can leverage them. Alex ------=_Part_2067_16671136.1207152247244 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Stefan S.,

Do we use a secondary cache for Studio? Just wondering because of the performance issues someone noted on the user list when dealing with a very large directory.  The idea occurred to me that the JDBM code for JdbmTable and JdbmIndex could potentially be used by Studio to help solve some of the caching problems.  If this is something you think will help we can move this code into shared so both the server and Studio can leverage them.

Alex
------=_Part_2067_16671136.1207152247244--