"Jonathan K. Weedon" wrote:
>
> As you say: "CMP can have ... performance limitations unless you cut some
> dangerous corners or you have a fairly complex CMP caching architecture."
> That is, if you don't do things properly, you will either have terribly
> slow CMP behavior, or incorrect CMP behavior. (Or, in the case of one
> leading vendor, both.) So yes, you have to do it right, to make it fast.
> But the correlary is that if you do take the time to do it right, it will
> be fast.
Are you are of any EJB servers that have "done it right" for standard EJB 1.1
CMP, in such a way that update transactions never commit if they were based
on stale data, transaction retry is automatic, and for read-only transactions
you can specify a maximum time window for possibly stale data?
________________________________________________________________________________
Evan Ireland Sybase EAServer Engineering [EMAIL PROTECTED]
Wellington, New Zealand +64 4 934-5856
===========================================================================
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".
