[
https://issues.apache.org/jira/browse/SLING-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16350310#comment-16350310
]
Timothee Maret commented on SLING-7168:
---------------------------------------
I have looked at the existing internal APIs in
{{org.apache.sling.distribution.core}} bundle and exported the minimal set to
allow implementing a agent in a separate bundle. The patch that does it is
available here
https://github.com/apache/sling-org-apache-sling-distribution-core/compare/SLING-7168
The patch does not modify the {{org.apache.sling.distribution.api}} bundle,
only the {{org.apache.sling.distribution.core}} one.
{{org.apache.sling.distribution.core}} exports are typically hidden from
customer access via the api controller.
The patch splits between consumer types (meant to be implemented) and provider
types.
[~teofili], [~simone.tripodi] could you have a look at it ?
> Allow to implement custom distribution agents/queues
> ----------------------------------------------------
>
> Key: SLING-7168
> URL: https://issues.apache.org/jira/browse/SLING-7168
> Project: Sling
> Issue Type: Improvement
> Components: Content Distribution
> Affects Versions: Content Distribution Core 0.2.8
> Reporter: Timothee Maret
> Assignee: Timothee Maret
> Priority: Major
> Fix For: Content Distribution Core 0.2.12, Content Distribution
> API 0.4.0
>
>
> Currently, it is not possible to implements distribution agents and queues,
> implemented in another bundle than the {{org.apache.sling.distribution.core}}
> bundle.
> Implementing a custom distribution agent outside of the
> {{org.apache.sling.distribution.core}} bundle is useful when leveraging an
> ad-hoc communication layer.
> This issue is about allowing to plug an external distribution agent/queue
> provided via a separate bundle.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
