| I think this is another one of those "difference in perspective" things - specifically from Hibernate's perspective versus the providers perspective. From Hibernate's perspective, this is simply an observer/handler that the caching provider would like to have notified of transaction events. It is really just a specialized Synchronization. And just like Synchronization there are different perspectives... a particular Synchronization impl might in fact be used as a transaction-local storage, but that is not intrinsic to the notion of Synchronization - a Synchronization could very well just log traces or collect stats or ... So from the specific perspective of hibernate-infinispan (or infinispan-hibernate-cache), sure this could be called a "storage". But again that is from that limited perspective. I am looking for the generalized concept name (Synchronization) rather than an implementation-specific name. Since I think "Synchronization" is a term we all understand in this context, maybe it is best to incorporate that term here... CacheTransactionSynchronization? "Context" as a term here is meaningless enough to allow it to cover either definition/perspective - which of course is both its pro and con. I'm ok with either, just throwing it out there since I think it is better to have a more immediately meaningful name whenever possible |
