WG: [Objectbridge-developers] Reader/Writer Locks and other such stuff
Brought to you by:
thma
From: <tho...@it...> - 2000-12-06 08:27:52
|
-----Ursprüngliche Nachricht----- Von: Thomas Mahler [mailto:tho...@it...] Gesendet am: Dienstag, 5. Dezember 2000 17:59 An: Dixon-Peugh, David Betreff: AW: [Objectbridge-developers] Reader/Writer Locks and other such stuff > -----Ursprüngliche Nachricht----- > Von: obj...@li... > [mailto:obj...@li...]Im Auftrag > von Dixon-Peugh, David > Gesendet am: Dienstag, 5. Dezember 2000 15:21 > An: 'Mahler Thomas'; 'obj...@li...' > Betreff: RE: [Objectbridge-developers] Reader/Writer Locks and other > such stuff > > If we have multiple strategies for locking, then should we have > different strategies for different classes? > > If a class requires a higher level of isolation, it doesn't seem > like too much trouble to give it to them. (Perhaps the class is > suceptable to race conditions?) > > -----Original Message----- > From: obj...@li... > [mailto:obj...@li...]On Behalf Of > Mahler Thomas > Sent: Tuesday, December 05, 2000 4:56 AM > To: dp...@mi... > Cc: Dixon-Peugh, David; obj...@li... > Subject: AW: [Objectbridge-developers] Reader/Writer Locks and other > such stuff > In the EJB specification it's possible to define isolation levels on a per bean (class) base, to give maximum flexibility to the application developer. If it's a good idea for EJB it will also be a good idea for OJB ;-) Thomas |