[Persistence-sig] getting started

[Phillip J. Eby]

At 04:50 PM 7/10/02 -0700, Ilia Iourovitski wrote:
>Based upon your comments you need to completly
>different thing:
>1. Transaction monitor, to which you can register
>different providers. Probably heuristic commit too.
>In Java world it is JTA spec and Tyrex as example.
>In case if you mixing SQL, LDAP you xa transactions
>and
>two-way commit protocol.

Yes, and the existing ZODB4 Transaction package supports two-phase commit 
across multiple providers.  I just find its protocol for doing it annoying 
in some ways.


>2. For slow pesristence providers you need proxies,
>mapping meta info, lazy loading, lazy collection.
>Loading by id, by query.
>Usuall OR Mapper stuff.

Yes, and I've designed and/or written all that, except for the proxy or 
base class, for which I use ZODB4's Persistence package.


>And what about locks in case of RDBMS.

I don't think there's anything special needed at the persistence level to 
handle this.


>All of those thing are out of scope of persistence-sig.

Item 2 things, yes, item 1 things no.  And even item 2's stuff has to be 
*capable* of being *done* with the SIG's output.  I don't need anybody to 
write those things; I just want to base my work for them on a solid 
mechanism for detecting access and changes to objects, and a solid API for 
interacting with a transaction object.