Re: Caching of read-only DB contents in an EJB

[Lahooti, Hamid]

Laird
>>http://www.beasys.com/products/weblogic/server/clustering.pdf
Here's an excerpt from above document:

"Database-oriented replication. One approach to state maintenance is to keep
the state in a database or other persistent store.
This is particularly suitable for persistent components...
The activation service can avoid concurrency conflicts here simply by
relying on underlying database locking. In a WebLogic cluster, EJB entity
beans default to this approach."

"A related approach is to maintain a write-through cache, which keeps a
current copy of the state in memory to avoid subsequent reads. This makes it
considerably harder to avoid concurrency conflicts, and doing so can
interfere with scalability."

I can't see how my earlier post conflicts with what is said in this
document.

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".