[
https://issues.apache.org/jira/browse/SLING-10585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothee Maret updated SLING-10585:
-----------------------------------
Fix Version/s: Content Distribution Journal Messages 0.5.0
> Add support for invalidation requests
> -------------------------------------
>
> Key: SLING-10585
> URL: https://issues.apache.org/jira/browse/SLING-10585
> Project: Sling
> Issue Type: New Feature
> Components: Content Distribution
> Reporter: Timothee Maret
> Assignee: Timothee Maret
> Priority: Major
> Fix For: Content Distribution Journal Core 0.1.26, Content
> Distribution API 0.7.0, Content Distribution Journal Messages 0.5.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Caching invalidation is typically triggered by content distribution, after
> processing an `ADD` or `DELETE` distribution request. When distributing
> referenced content, invalidation must also include on the referencing
> resources. To support this use case, we'll add support for a new type of
> distribution request that invalidates the caches without importing content.
> To support this, the org.apache.sling.distribution.DistributionRequestType
> API will be extended with
> {code:java}
> /**
> * Action type for invalidating content
> */
> INVALIDATE,
> {code}
> The PackageMessage.ReqType will be extended with the new INVALIDATION type.
> The DistributionPublisher will handle the invalidation distribution requests
> by sending a package message with the INVALIDATION type and no payload (like
> the DELETE package messages).
> The DistributionSubscriber will process invalidation messages by raising
> imported events and invoking the import post processors.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
