[ 
https://issues.apache.org/jira/browse/SLING-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16350399#comment-16350399
 ] 

Simone Tripodi edited comment on SLING-7168 at 2/2/18 2:30 PM:
---------------------------------------------------------------

The patch looks great and I even think that moving interfaces to the API bundle 
shouldn't be harmful for backward compatibility... WDYT?

It would be just a matter of not mixing up stuff , would it make sense?

Anyway, I am +1 for checking the modifications in the repo, thanks a lot for 
your work [~marett]! :)


was (Author: simone.tripodi):
The patch looks great and I even think that moving interfaces to the API bundle 
shouldn't be harmful for backward compatibility... WDYT?

It would be just a matter of not mixing up stuff , would it make sense?

Anyway, I am +1 for checking-in the modifications on the repo, thanks a lot for 
your work [~marett]! :)

> 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)

Reply via email to