[
https://issues.jboss.org/browse/ISPN-858?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño commented on ISPN-858:
---------------------------------------
Yeah, reached the same conclusion in JBPAPP-5715. I was thinking of using along the lines
of the version use in HotRod/Memcached, which integrates cluster node information if
available, and an counter. Why would relying on a counter lead to unnecessary cache
invalidation? I'd imagine that the counter would get updated whenever the new
MIMECacheEntry gets updated which happens on a put() call
I can only think of too much invalidation happening if the counter was incremented in
spite of the contents not changing.
MIMECacheEntry requires a version
---------------------------------
Key: ISPN-858
URL:
https://issues.jboss.org/browse/ISPN-858
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 4.2.0.Final, 5.0.0.ALPHA1
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 4.2.1.Final, 5.0.0.BETA1
ETag calculation requires MIMECacheEntry to carry a version similar to HotRod/Memcached
in order to avoid collisions with closely followed updates.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira