[ https://issues.apache.org/jira/browse/SLING-8065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothee Maret resolved SLING-8065. ----------------------------------- Resolution: Won't Do Instead of extracting trait APIs, we used a queue meta data approach to specify the queue capabilities in SLING-8086. > Introduce ReadOnlyDistributionQueue API > --------------------------------------- > > Key: SLING-8065 > URL: https://issues.apache.org/jira/browse/SLING-8065 > Project: Sling > Issue Type: Improvement > Components: Content Distribution > Affects Versions: Content Distribution Core 0.3.4 > Reporter: Timothee Maret > Assignee: Timothee Maret > Priority: Major > Fix For: Content Distribution Core 0.3.6 > > Time Spent: 10m > Remaining Estimate: 0h > > We currently export an > [SPI|https://github.com/apache/sling-org-apache-sling-distribution-core/tree/master/src/main/java/org/apache/sling/distribution/queue/spi] > with a fully editable queue, > [DistributionQueue|https://github.com/apache/sling-org-apache-sling-distribution-core/blob/master/src/main/java/org/apache/sling/distribution/queue/spi/DistributionQueue.java]. > Some distribution queue implementation are read-only meaning that they don't > provide the ability to add/remove items. Example of such read-only queue is > an implementation on top of an append only messaging service. > In this issue, I suggest to introduce add and export the > {{ReadOnlyDistributionQueue}} interface. The existing read-only method > signatures from {{DistributionQueue}} would be moved from > {{DistributionQueue}} to {{ReadOnlyDistributionQueue}}. {{DistributionQueue}} > would extend from {{ReadOnlyDistributionQueue}}. This change is backward > compatible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)