From version < 17.1 >
edited by Thomas Mortagne
on 2020/01/27 18:12
To version < 18.1
edited by Thomas Mortagne
on 2020/02/07 13:46
<
Change comment: Renamed back-links.

Summary

Details

Page properties
Content
... ... @@ -75,7 +75,7 @@
75 75  
76 76  Same than 2-A, but when a new event is triggered, the cache would not be cleared. Instead, the new event will be considered for each user, and added in the caches if the event is not filtered by the user preferences.
77 77  
78 -== [[Solution 2 - C: Store in a permanent storage the notifications for each user>>Proposal.NotificationsOptimization.NotificationStorage]] ==
78 +== [[Solution 2 - C: Store in a permanent storage the notifications for each user>>Proposal.NotificationsOptimization.NotificationStatusStorage.WebHome]] ==
79 79  
80 80  This title is not exactly what I meant. The idea is not to store each notification in a table (the event is already in the event stream store), but the "read" status of each event for each user, **when the event is recorded**.
81 81  

Get Connected