The Slide project ? which project are you talking about ? the one from Jakarta ?
Yes the resulting isolation level is similar to READ_COMMITED. -----Message d'origine----- De: Oliver Zeigermann A: OJB Users List Date: 10/12/2004 14:53 Objet: Re: Another implementation of the Two Level Cache This pretty much is the mechanism the Slide project uses. AFAIK the isolation level is similar to READ_COMMITTED, isn't it? Oliver On Fri, 10 Dec 2004 13:18:53 +0100, CLARAMONTE Jean-Baptiste <[EMAIL PROTECTED]> wrote: > Hello, > > As I was not satisfy with the implementation of the TwoLevelCache, > mainly because it was not isolating the object in use in a transaction > with others transactions, so I've tried to write another one and now I > would like too share it with the community. > For resuming here are the behavior of this cache : > When you retrieve an object a flat copy are made and the added in the > first level cache (a kind of broker session cache). > A call to store() will not immediately put the objet in the second > level cache but only in the first level (so this way other > transactions are isolated from update on the objet since your > transaction could finally abort) > Rollbacking a transaction simply clear the first level cache (the > broker session cache) > Commiting the transaction transfert the object from the first level > cache to the second level cache so that object update become visible > to other transactions. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] *** We scanned this email for malicious content *** *** IMPORTANT: Do not open attachments from unrecognized senders *** *** MailSystem ASTON *** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
