for java-to-java invalidation I successfully used OSCache with
JGroups. For non-java apps that change the data there are a few options:
1. A private URL in a webapp that a script can access that would cause
cache invalidation
2. A timer local to the app that checks a special table in DB that is
populated by the script on data changes.
3. A timer running in a remote Java app that checks a DB table, and
then notifies another app with JGroups.
4. etc.
Andrus
On May 5, 2008, at 11:21 AM, Andreas Pardeike wrote:
Hi,
I have an web application that serves html pages from a databases.
That database is manipulated from a perl program that runs from
within a proftpd ftp server. As a result, users can upload their
html pages via ftp and the web application displays them.
I want to cache the page queries in the web application but have
not found a good way to invalidate a certain page in the cache once
a user uploads a modified version of it.
I use:
- Tomcat on Linux
- Tapestry 5
- Cayenne 3
- Mysql 5
- Custom mod_exec perl script in proftpd
What is the best approach here?
/Andreas Pardeike
