Return-Path: <thma32@web.de>
Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm
Delivered-To: mailing list ojb-dev@db.apache.org
Received: (qmail 6687 invoked from network); 1 Apr 2003 06:11:11 -0000
Received: from smtp02.web.de (HELO smtp.web.de) (217.72.192.151)
  by daedalus.apache.org with SMTP; 1 Apr 2003 06:11:11 -0000
Received: from dialin-212-144-137-009.arcor-ip.net ([212.144.137.9]
 helo=web.de)
	by smtp.web.de with asmtp (TLSv1:RC4-MD5:128)
	(WEB.DE(Exim) 4.97 #53)
	id 190EzS-0003QC-00
	for ojb-dev@db.apache.org; Tue, 01 Apr 2003 08:11:22 +0200
Message-ID: <3E891F7B.7060402@web.de>
Date: Tue, 01 Apr 2003 07:11:23 +0200
From: Thomas Mahler <thma32@web.de>
Reply-To: thma@apache.org
Organization: Apache Foundation
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020903
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: OJB Developers List <ojb-dev@db.apache.org>
Subject: Re: Plans for implicit locking
References: <20030331214656.6634.qmail@web14402.mail.yahoo.com>
X-Enigmail-Version: 0.63.3.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Sender: thma32@web.de
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Hi Nuno,

For ODMG no, for JDO yes.

If someone volunteers to implement it for ODMG I won't object!
For JDO it's mandatory, but requires nasty things like bytecode-enhancement.

It is very easy to build objects in a "cooperative" way. That is, if a 
setter is called first obtain a write lock. The Odmg persistent 
collections are built in this way.

cheers,
Thomas


Nuno Marques wrote:
> Hye,
> 
> Are there any plans to support implicit locking (on object change, during transaction) for future versions of OJB?
> 
> Tia,
> 
> Nuno Marques
> 
> 
> 
> ---------------------------------
> Yahoo! Mail 
> O melhor e-mail gratuito da internet: 6MB de espa�o, antiv�rus, acesso POP3, filtro contra spam.