[
https://issues.apache.org/jira/browse/SLING-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13871922#comment-13871922
]
Carsten Ziegeler commented on SLING-3315:
-----------------------------------------
The nice thing about using the resource access gate is that it enforces all
acls meaning it controls who can read, write, delete etc. No need to add these
checks in own code all over the place and create a dependency to JCR
So I strongly suggest to switch to the resource access gate as this is the main
reason why we came up with it :)
A snapshot dependency to api is no problem
> Refactor replication HTTP API
> -----------------------------
>
> Key: SLING-3315
> URL: https://issues.apache.org/jira/browse/SLING-3315
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Reporter: Marius Petria
> Labels: replication
> Attachments: SLING-3315.1.patch, SLING-3315.patch
>
>
> Refactor HTTP API in order to access independently the configuration of an
> agent and the service API for an agent. This was needed because there are
> times when a configuration can exist without an agent being available (e.g.
> when the agent is not disabled).
> Proposed API:
> Managing configuration
> POST /system/replication/config/agent (creates and agent cofig)
> GET /system/replication/config/agent (retrieves all agents config)
> POST /system/replication/config/agent/{agentName} (updates and agent)
> GET /system/replication/config/agent/{agentName} (retrieves the agent
> config)
> DELETE /system/replication/config/agent/{agentName} (deletes an agent config)
> Managing agent
> POST /system/replication/config/agent/{agentName} (schedules a package
> for replication or removes one from the queue)
> GET /system/replication/config/agent/{agentName}/queue (lists the
> packages in the queue)
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
