You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Tommaso Teofili (JIRA)" <ji...@apache.org> on 2014/11/07 16:58:41 UTC

[jira] [Updated] (SLING-3833) Cleanup ReplicationAgent interface and ReplicationAgentConfiguration

     [ https://issues.apache.org/jira/browse/SLING-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tommaso Teofili updated SLING-3833:
-----------------------------------
    Fix Version/s: Content Distribution 0.1.0

> Cleanup ReplicationAgent interface and ReplicationAgentConfiguration
> --------------------------------------------------------------------
>
>                 Key: SLING-3833
>                 URL: https://issues.apache.org/jira/browse/SLING-3833
>             Project: Sling
>          Issue Type: Improvement
>          Components: Distribution
>            Reporter: Marius Petria
>            Assignee: Tommaso Teofili
>             Fix For: Content Distribution 0.1.0
>
>         Attachments: SLING-3833.patch
>
>
> ReplicationAgent should have a minimal interface. More specifically a client should be able to schedule a ReplicationRequest and to visualize the ReplicationQueues.
> If we decide that synchronous execution is needed then that should be properly implemented as the current version is not synchronous. 
> Also, agent configuration is particular to the SimpleReplicationAgent implementation. It is true that it is the single implementation that we have but  it cannot be an API unless we decide on a fixed set of properties that all agent implementations should have. Either way configurations are currently accessible through the custom resource provider.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)