This issue has been created
There is 1 update, 1 comment.
 
 
XWiki Platform / cid:jira-generated-image-avatar-184ab8ee-78e1-486d-93d8-b25440ac3d83 XWIKI-22207 Open

Allow async data to be invalidated by notification filter preference change

 
View issue   ยท   Add comment
 

Issue created

 
cid:jira-generated-image-avatar-891f47e6-951a-4e77-b509-001cf397218a Simon Urli created this issue on 03/Jun/24 09:29
 
Summary: Allow async data to be invalidated by notification filter preference change
Issue Type: cid:jira-generated-image-avatar-184ab8ee-78e1-486d-93d8-b25440ac3d83 Improvement
Affects Versions: 15.10.10
Assignee: Unassigned
Components: Rendering - Async
Created: 03/Jun/24 09:29
Priority: cid:jira-generated-image-static-major-e3d6140d-11d2-4fc6-a83d-5e7079149ceb Major
Reporter: Simon Urli
Description:

Notification filter preferences are currently saved in a custom DB and not in documents so the async rendering mechanism is not called at all whenever those data changed. In general the data don't have impact on the rendering of the pages so it's ok, except for the UI related to the administration of those data and for computation of the watch page status: we cannot make those async / cache because there's an invalidation problem.

We'd need to add some APIs to allow those data to be invalidated when modified so that we can start using async / cache in the various UIs using them.

 
 

1 update

 
cid:jira-generated-image-avatar-891f47e6-951a-4e77-b509-001cf397218a Changes by Simon Urli on 03/Jun/24 09:30
 
Component: Notifications
 
 

1 comment

 
cid:jira-generated-image-avatar-891f47e6-951a-4e77-b509-001cf397218a Simon Urli on 03/Jun/24 09:30
 

Discussion about how to implement that and the original issue on https://matrix.to/#/!ikPtGZaGWtyblizzlR:matrix.xwiki.com/$1716986172643phhIg:matrix.xwiki.com?via=matrix.org&via=matrix.xwiki.com&via=helsinki-systems.de