On Fri, 28 Jul 2000 09:07:55 -0400, James Cook <[EMAIL PROTECTED]>
wrote:
>> The conclusion is that it is impossible to use
>> * optimistic concurrency control in the container
>> container and
>> * caching of Entity data and
>> * SERIALIZABLE isolation level in the DB
>
>What serious, enterprise application can rely on the caching of entity data?
I don't know. Does that impact the above conclusion? I just said that
the above combination is impossible.
>Of course there are some specialized apps (i guess) that truly *own* their
>data and can use Option A, but for most *real world* apps, this is a pipe
>dream. Even in a new application that does not share it's data now, you
>can't predict what the future requirements for that data may be.
If the point of access is the EJB-system, which is not unlikely, then it
seems ok to use entity caching for performance.
But the real point is that since the EJB-system as a whole need not be
reliant on this particular feature, why worry? Use it if possible, and
don't use it if it's not possible, or change between the two as
requirements change.
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
===========================================================================
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".
