[MGNLCACHE-79] Implement cache listeners Created: 06/Nov/14 Updated: 07/Nov/14 Resolved: 06/Nov/14 |
|
| Status: | Closed |
| Project: | Cache Modules |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Roman Kovařík | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: |
| Comments |
| Comment by Jan Haderka [ 06/Nov/14 ] |
|
While it's useful to have listener to react on put/get/clear I would definitively not allow listening on hasElement ... first because it's internal detail and not anyones business to react on check whether something exists or not and second because that method opens a loophole to cause deadlock if someone tries to get element from cache in the listener just after call to hasElement while using key provided in the method. |