Return-Path: Delivered-To: apmail-db-ojb-dev-archive@www.apache.org Received: (qmail 22595 invoked from network); 6 Jul 2004 09:24:04 -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:24:04 -0000 Received: (qmail 53891 invoked by uid 500); 6 Jul 2004 09:24:22 -0000 Delivered-To: apmail-db-ojb-dev-archive@db.apache.org Received: (qmail 53840 invoked by uid 500); 6 Jul 2004 09:24: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 53802 invoked by uid 99); 6 Jul 2004 09:24:21 -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:24:20 -0700 Received: (qmail 22526 invoked from network); 6 Jul 2004 09:24:00 -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:24:00 -0000 Message-ID: <40EA6FD3.6070203@apache.org> Date: Tue, 06 Jul 2004 11:24:35 +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: Move new services to kernel 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 all, think (after Brian's auto-dirtying suggestion) we should discuss in general about moving services from OTM/ODMG to the kernel. Which services are useful in kernel which not. One thing is object status detecting (e.g. used by Brian auto-dirtying), classes help to make object snapshots should be available in kernel (Maybe something like a SnapshotBuilder and SnapshotStrategy). Another service is pessimistic locking. Why not move it to kernel, then it will be possible to use pessimistic locking in PB-api. No automatic locking, only the locking service so that PB-api user can lock objects and can detect if objects are locked. Currently the locking implementations used by ODMG and OTM are bound to their API, why not make it independent and only pass String objects to the locking service, e.g. lock(String tx_key, String obj_oid)? This will make pessimistic locking independent and the implementation of distributed locking maps will be easier. regards, Armin --------------------------------------------------------------------- To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org For additional commands, e-mail: ojb-dev-help@db.apache.org