You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Timothee Maret (Jira)" <ji...@apache.org> on 2021/07/06 09:22:00 UTC
[jira] [Created] (SLING-10585) Add support for invalidation
requests
Timothee Maret created SLING-10585:
--------------------------------------
Summary: 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
Fix For: Content Distribution Journal Core 0.1.18, Content Distribution Core 0.4.8, Content Distribution Journal Messages 0.3.2, Distribution API 0.6.0
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.3.4#803005)