Return-Path: Delivered-To: apmail-db-ojb-dev-archive@www.apache.org Received: (qmail 28519 invoked from network); 18 Sep 2004 08:58:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 18 Sep 2004 08:58:22 -0000 Received: (qmail 47960 invoked by uid 500); 18 Sep 2004 08:58:21 -0000 Delivered-To: apmail-db-ojb-dev-archive@db.apache.org Received: (qmail 47876 invoked by uid 500); 18 Sep 2004 08:58:21 -0000 Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "OJB Developers List" Reply-To: "OJB Developers List" Delivered-To: mailing list ojb-dev@db.apache.org Received: (qmail 47862 invoked by uid 99); 18 Sep 2004 08:58:20 -0000 X-ASF-Spam-Status: No, hits=-10.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [209.237.227.194] (HELO minotaur.apache.org) (209.237.227.194) by apache.org (qpsmtpd/0.28) with SMTP; Sat, 18 Sep 2004 01:58:20 -0700 Received: (qmail 28490 invoked from network); 18 Sep 2004 08:58:19 -0000 Received: from localhost.hyperreal.org (HELO ?127.0.0.1?) (127.0.0.1) by localhost.hyperreal.org with SMTP; 18 Sep 2004 08:58:19 -0000 Message-ID: <414BF8B7.4070307@apache.org> Date: Sat, 18 Sep 2004 10:58:31 +0200 From: Armin Waibel User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: OJB Developers List Subject: Re: [OJB1.0.x] odmg improvement, locking-package move References: <414B8B92.3020602@apache.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: localhost.hyperreal.org 1.6.2 0/1000/N X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi Brian, Brian McCallister wrote: > How would you access the locking stuff outside of ODMG? Talk to the lock > manager directly? > There will be a org.apache.ojb.broker.locking.LockManager interface expects Object arguments for 'key' and 'lockedObject' and on odmg-level the "old" LockManager interface (expect TransactionImpl and Object arguments) further on exists. In ...odmg.locking.LockManagerOdmgImpl a broker.locking.LockManagerXYZImpl instance will be wrapped and the ...odmg.locking.LockManagerFactory does internal create and configure the PB-locking stuff and return LockManagerOdmgImpl. So on odmg-level nothing will be changed (except locking package and some other tweak ;-)). regards, Armin > -Brian > > On Sep 17, 2004, at 9:12 PM, Armin Waibel wrote: > >> Hi all, >> >> some month ago we talked about the odmg-locking package. The >> suggestion was to make the locking stuff independent from the odmg >> implementation and move it to the to the kernel. So in future all >> top-level api can use this stuff. >> Locally I made these changes + other cleanup using 1.0.x branch. All >> tests pass and the odmg performance increase more than 30%! >> (perf-test target for odmg: before 17sec, after 12,5sec) >> >> Should I check in these changes for 1.0.2 release? >> >> regards, >> Armin >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org >> For additional commands, e-mail: ojb-dev-help@db.apache.org >> >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org > For additional commands, e-mail: ojb-dev-help@db.apache.org > > > --------------------------------------------------------------------- To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org For additional commands, e-mail: ojb-dev-help@db.apache.org