[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnue-dev] GEAS Object Life Circle Proposal
From: |
Jan Ischebeck |
Subject: |
Re: [Gnue-dev] GEAS Object Life Circle Proposal |
Date: |
Tue, 14 May 2002 18:54:11 +0200 |
User-agent: |
Mutt/1.3.28i |
Hallo Reinhard,
On Tue, May 14, 2002 at 05:11:30PM +0200, Reinhard Mueller wrote:
> 1. Not sure if we should generally lock an object when a "local copy" is
> created. I think we should support something like that we can read
> locked an non-locked.
In my test implementation the transaction directly access the global
object for reading. Just for writing a local object is created.
> 2. I don't understand the difference between "active" and "inactive"
> state in the left half of the drawing.
inactive: the object is just data in the database
active: the object is an python instance, which can react on function
calls etc.
Yesterday Daniel Baumann told me that odmg.txt defines three types of locks:
readlock, writelock and upgradelock (=readlock+ intensional write lock).
It will be a minor change to add these to the diagram.
Jan Ischebeck