[KULRICE-5967] Investigate whether we should publish methods on services to flush caches Created: 14/Nov/11 Updated: 23/Feb/12 Resolved: 05/Jan/12
|Project:||Kuali Rice Development|
|Component/s:||Development, Version Compatibility|
|Fix Version/s:||2.0.0-b6, 2.0|
|Security Level:||Public (Public: Anyone can view)|
|Reporter:||Jeremy Hanson||Assignee:||Jeremy Hanson|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|KAI Review Status:||Not Required|
|KTI Review Status:||Not Required|
Currently cache's are flushed on update and create methods, but should we have a method that flushes the cache with a call? It seems possible that some institutions would have a batch job that doesn't use the service for crud (db updates?), and it seems like in that instance there should be an easier way for them to clear the cache.
|Comment by Eric Westfall [ 22/Nov/11 ]|
Bulk update of incomplete 2.0.0-b2 issues to just a 2.0 fix version.
|Comment by Eric Westfall [ 05/Jan/12 ]|
My opinion on this is that we should not be doing this as part of the main service contract. As part of some sort of auxiliary administration api, perhaps (assuming it's needed). But I think that the idea with the services is that the caching is an implementation detail so publishing methods to facilitate manual cache flushing on the api constitutes a leaky abstraction to me. I'm going to resolve this issue, but feel free to discuss further if you think otherwise.
|Comment by Jessica Coltrin (Inactive) [ 23/Feb/12 ]|
Closing since these items are now in the release notes.