On Sat, 29 Jul 2000 10:22:28 -0400, Peter Booth
<[EMAIL PROTECTED]> wrote:
>Can you add some more information about how one might
>approach implementing a synched cache with minimum overhead?
I'll try, but it's hard to explain in detail. Let each cluster node to
Option A (i.e. cache data). When a change has been made in an entity in
one node, the other nodes are notified that the entity with the
particular pk has changed. If they have that entity the data is marked
as invalid. When a new transaction with that entity is started on one of
the "flushed" cluster nodes, its data will simply be reloaded from the
db. That's the basic idea anyway.
There are more details involved with how to make sure that the nodes
don't overwrite each others data if two concurrent tx's modify the same
entity.
/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".
