On Mon, 25 Jun 2001 12:24:59 -0700, Cedric Beust <[EMAIL PROTECTED]> wrote:
>> From: A mailing list for Enterprise JavaBeans development
>> [mailto:[EMAIL PROTECTED]]On Behalf Of John Harby
>
>> About the competing process consideration. Suppose I *knew* that no
>> non-appserver process would modify my CMP table.
>
>Okay, so you have two nodes in your cluster, in which all entity beans
>compete for the same tables.
>
>> Couldn't I have a
>> low-maintenance bitmap replicated in the cluster. This bitmap
>> would tell me the status of the CMP tables so that I could simply check
>the
>> bitmap (n x n binary matrix) before my load went to the db? I would try to
>argue much on
>> this because I know there are probably many proprietary optimizations in
>> place that would nullify this benefit.
>
>It seems to me that you are basically describing optimistic locking at the
>container level, and yes, I agree, it is useful.
Optimistic locking at the container would be great indeed, but how about optimistic
locking at the DB level?
If we are working in a cluster with n nodes, is there any need to ejbLoad an entity
more than once per transaction then?
Regards,
Peter Verkest
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
