[jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1175) Option.forceCall(A)sync
[ http://jira.jboss.com/jira/browse/JBCACHE-1175?page=comments#action_12377179 ]
Manik Surtani commented on JBCACHE-1175:
----------------------------------------
Go ahead with this then if you have the code in place and have the time to write the tests
for it. Let me know if not, attach the patches you have and leave it with me.
Option.forceCall(A)sync
-----------------------
Key: JBCACHE-1175
URL: http://jira.jboss.com/jira/browse/JBCACHE-1175
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 2.1.0.GA
Add an option to allow an individual call to go async/sync when the cache overall is
configured for the opposite.
This would only be relevant to calls not running in a tx; transactional replication would
use the standard semantic configured for the cache.
Use case for this is Hibernate timestamp region replication, which needs to go async,
while all other Hibernate 2nd level cache traffic goes sync. A good region-based cache
impl would solve the problem as well, but that will surely take quite a while to implement
a while while doing it via an Option looks quite trivial.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira