T
Timo Nentwig
I need to track changes made to content by the CMS in order to
invalidate cache keys (JCS and OSCache). My approach is to use a Map
(Commons Collections MultiHashMap): key is the ID of the content changed
and the values are the cache keys associated with the content.
Access to the Map is performance-critical and must be synchronized.
The servers run in clusters and there are multiple dedicated server
clusters (different projects) accessing the same content hence if
content has changed everybody must be notified.
Two problems raise:
1) How do I share the Map in a and across the clusters? The answer is
probably something related to JNDI.
2) How am I doing the notification? Is JMS a good idea here? And if so
how would you implement it?
Also consider that the Map must be made persistent for a matter of
server restarts.
Thanks a lot for suggestions!
Timo
invalidate cache keys (JCS and OSCache). My approach is to use a Map
(Commons Collections MultiHashMap): key is the ID of the content changed
and the values are the cache keys associated with the content.
Access to the Map is performance-critical and must be synchronized.
The servers run in clusters and there are multiple dedicated server
clusters (different projects) accessing the same content hence if
content has changed everybody must be notified.
Two problems raise:
1) How do I share the Map in a and across the clusters? The answer is
probably something related to JNDI.
2) How am I doing the notification? Is JMS a good idea here? And if so
how would you implement it?
Also consider that the Map must be made persistent for a matter of
server restarts.
Thanks a lot for suggestions!
Timo