Return-Path: Delivered-To: apmail-db-ojb-dev-archive@www.apache.org Received: (qmail 22458 invoked from network); 6 Jul 2004 09:23:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 6 Jul 2004 09:23:56 -0000 Received: (qmail 52852 invoked by uid 500); 6 Jul 2004 09:24:04 -0000 Delivered-To: apmail-db-ojb-dev-archive@db.apache.org Received: (qmail 52600 invoked by uid 500); 6 Jul 2004 09:23:59 -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 52332 invoked by uid 99); 6 Jul 2004 09:23:56 -0000 X-ASF-Spam-Status: No, hits=-0.1 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.27.1) with SMTP; Tue, 06 Jul 2004 02:23:54 -0700 Received: (qmail 22073 invoked from network); 6 Jul 2004 09:23:33 -0000 Received: from localhost.hyperreal.org (HELO ?127.0.0.1?) (127.0.0.1) by localhost.hyperreal.org with SMTP; 6 Jul 2004 09:23:33 -0000 Message-ID: <40EA6FB9.1070209@apache.org> Date: Tue, 06 Jul 2004 11:24:09 +0200 From: Armin Waibel User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502) X-Accept-Language: en-us, en MIME-Version: 1.0 To: OJB Developers List Subject: Re: AutoDirty in PB References: <9C75E19C-CEF1-11D8-A267-000A95782782@forthillcompany.com> In-Reply-To: <9C75E19C-CEF1-11D8-A267-000A95782782@forthillcompany.com> 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, +1, I don't know your implementation in detail, but sounds good to me. Is it configurable at runtime (enable/disable auto-dirtying)? Armin Brian McCallister wrote: > I have a PersistenceBroker implementation (really just a set of > listeners on the regular PB) which handle auto-dirtying at the > persistence broker level via copy-on-read and compare-on-commit. > > It is less functional than the OTM in that it doesn't handle isolation > etc, just performs its behavior at the PB level. This is identical > behavior to the Hibernate Session, which a lot of people seem to like, > so I was wondering, now that 1.0 is out, if there was any interest in > making this available in the OJB directly, or simply work on the OTM > level. Advantage is that it is more performant and much less code than OTM. > > -Brian > > > > --------------------------------------------------------------------- > 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