Sounds great Praveen, my only concern would be with message/network
traffic overhead in a large environment. But that's situational problem.

-----Original Message-----
From: A mailing list for Java(tm) 2 Platform, Enterprise Edition
[mailto:J2EE-INTEREST@(protected)
Sent: Friday, January 09, 2004 8:35 AM
To: J2EE-INTEREST@(protected)
Subject: Re: Shared cache best practices?


After reading the message in this thread, I think people are making a
simple problem too complex. Even I would stay away from EJBs and stuff
just for the sake of caching. We use a caching toll called "oscache". It
does exactly what the original poster wants.

Oscache uses javagroups underneath for messaging. It works for me in a
clustered environment perfectly for me. Basically what OsCache does is:
It sends notifications to all servers that are bind to a particular
address, when a particular object in a cache (lets say on server1) is
flushed. This notification flushes the same object in each server's
cache. That way stale date is flushed in all servers.

Its very simple to use and I think it solves the exact problem.

You can look at oscache at http://opensymphony.com/oscache/. The tool
can also use JMS for sending notifications.

Praveen

========================================================================
===
To unsubscribe, send email to listserv@(protected)
body of the message "signoff J2EE-INTEREST". For general help, send
email to listserv@(protected)
"help".

===========================================================================
To unsubscribe, send email to listserv@(protected)
of the message "signoff J2EE-INTEREST". For general help, send email to
listserv@(protected)".