I blame the server when it's vendor promises optimistic concurrency and doesn't
really provide it. You may be having problems with my statement because you do
not agree with the statement that deadlocks cannot occur with optimistic
concurrency control. I don't care what actual products do that claim optimistic
concurrency, if they deadlock then the claims are false.
--Victor
"Lahooti, Hamid" wrote:
> >If your server vendor claims to support optimistic concurrency and
> >you end up with deadlocks, you need to find another product.
>
> How can you blame the server for an application's mishandling
> of its transaction logic? The best way to avoid deadlocks is to ensure
> orderly access to shared resources. It's in the application design.
>
> >Victor Langelo
>
> Regards,
> Hamid
>
> ===========================================================================
> 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".
===========================================================================
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".
