Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 65751 invoked from network); 4 Apr 2008 06:18:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Apr 2008 06:18:57 -0000 Received: (qmail 28219 invoked by uid 500); 4 Apr 2008 06:18:57 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 28201 invoked by uid 500); 4 Apr 2008 06:18:57 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 28192 invoked by uid 99); 4 Apr 2008 06:18:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2008 23:18:57 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of plinskey@gmail.com designates 64.233.184.228 as permitted sender) Received: from [64.233.184.228] (HELO wr-out-0506.google.com) (64.233.184.228) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Apr 2008 06:18:15 +0000 Received: by wr-out-0506.google.com with SMTP id c57so2528518wra.9 for ; Thu, 03 Apr 2008 23:18:13 -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:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=bb3sNo9VtoNR6OnbU7pOFOpUbYlspHUtawm9QG7+U0M=; b=MOZNzykVrQaW1YPLjZ+0fbJLiDmiZzHdHh/RsWZlHolSU+APHUWNF7SDgzvf8Yl2XPEGKtXjRMByqV3UijXzQ27HajSpFmpim3gBdjNhgJq0SPERmt521FGgxVI63nmQmTFAakjSCjIgvmHeZ3sFnpOhw5kFrsduQMlaMWVESyY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=k2H0TDoMAXjgt3U2NOCkUNUJfc6vkoRSsgBYFvu+c00vDnmhjjRGr/iYYVZjL9G3Ias3PpjBSV08DCMFXQCebP33p1JRBBtNOlo2epYP37kcAzVW2z9+ubSswzTFsf6Vb+g8ct0TPMtKIBU0E3a8JqWYE+Yvlk5tUHx2lJQ7t2o= Received: by 10.150.205.13 with SMTP id c13mr423151ybg.66.1207289893572; Thu, 03 Apr 2008 23:18:13 -0700 (PDT) Received: by 10.150.158.20 with HTTP; Thu, 3 Apr 2008 23:18:08 -0700 (PDT) Message-ID: <7262f25e0804032318p36693e39y83da1e4bbc1e651f@mail.gmail.com> Date: Thu, 3 Apr 2008 23:18:08 -0700 From: "Patrick Linskey" To: dev@openjpa.apache.org Subject: Re: difference between datacache and systemDataCache? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <7262f25e0804031142q461619f3lf376c86e8c55a4f6@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org > So just to be sure - > Is OpenJPA going to keep the concept of multiple named cache in place at > the StoreManager level at least? > Is what you meant only from the perspective of the datacache layer itslef? > (I Hope it is ;) ). Yes. > Why does OpenJPA do not have multiple named cache capability in its > datacache layer? Historical reasons, basically. OpenJPA is a subset of Kodo; multiple named caches was one of the things that was kept out of OpenJPA. -Patrick On Thu, Apr 3, 2008 at 3:31 PM, wrote: > Patrick - thanks a lot for the answer - it helps a great deal understand > the design of openjpa. > > But - please - could clarify one part: > > You said - "OpenJPA has a single DataCache" - this is correct in how the > data cache is coded currently. But reading the source code of the > StoreManager - I can see that OpenJPA understand the concept of multiple > named cache very well. In fact I love the fact that the StoreManager > aggregate all changes at the cache level (based on name) before propagating > them to the datacache manager (it calls getCache(name)). This is fantastic > for me becuase since I am doing a new cache plug in for open jpa I can take > the call by the CacheStore and send one call to the cache and do the work > for the entire collection for a particular cache - This is a far more > efficient approach. > > So just to be sure - > Is OpenJPA going to keep the concept of multiple named cache in place at > the StoreManager level at least? > Is what you meant only from the perspective of the datacache layer itslef? > (I Hope it is ;) ). > Why does OpenJPA do not have multiple named cache capability in its > datacache layer? > > F > > > > > "Patrick Linskey" > om> To > dev@openjpa.apache.org > cc > 04/03/2008 11:42 > AM Subject > Re: difference between datacache > and systemDataCache? > Please respond to > dev@openjpa.apach > e.org > > > > > > > > > > > What is the exact concept behind the system wide datacache? > > Is it just a simplified way to get a proxy to all the caches in case > > someone needs it and does not know which cache exactly they should get? > It > > seems to just be fullfiling this role. > > Yep, that's its job. Since OpenJPA has just a single data cache (vs. > Kodo's multiple named caches), in OpenJPA this is not a proxy. > > > Why does the broker gets a reference to the systemDataCache when it is > > created? > > What code in particular are you asking about? > > -Patrick > > On Thu, Apr 3, 2008 at 10:29 AM, wrote: > > > > What is the exact concept behind the system wide datacache? > > Is it just a simplified way to get a proxy to all the caches in case > > someone needs it and does not know which cache exactly they should get? > It > > seems to just be fullfiling this role. > > > > Why does the broker gets a reference to the systemDataCache when it is > > created? > > > > F > > > > > > > > -- > Patrick Linskey > 202 669 5907 > > > -- Patrick Linskey 202 669 5907