 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Struts - A MVC web framework | | Tomcat - JSP/Servlet container | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | | JSP - A mailing list about Java Server Pages specification and reference | |
Struts & Hibernate
|
|
|
| | | SV: Shared cache best practices? | SV: Shared cache best practices? 2004-01-09 - By Erik Beijnoff
Back
>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
>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.
Ohhhh that's nice. I'll check it out. Thanks.
/Erik Beijnoff
===========================================================================
To unsubscribe, send email to listserv@(protected) and include in the body
of the message "signoff J2EE-INTEREST". For general help, send email to
listserv@(protected) and include in the body of the message "help".
|
|
|
