[jira] [Updated] (SLING-3356) Expose the import queue for reverse replication through ReplicationAgent interface

2014-11-07 Thread Tommaso Teofili (JIRA)

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

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

> Expose the import queue for reverse replication through ReplicationAgent 
> interface
> --
>
> Key: SLING-3356
> URL: https://issues.apache.org/jira/browse/SLING-3356
> Project: Sling
>  Issue Type: Improvement
>  Components: Distribution
>Reporter: Marius Petria
>Assignee: Tommaso Teofili
> Fix For: Content Distribution 0.1.0
>
> Attachments: SLING-3356.1.patch, SLING-3356.2.patch, 
> SLING-3356.3.patch, SLING-3356.patch
>
>
> The replication agent should have 3 main queues (the request queue, the 
> transport queue and the response queue). These queues should be accessible 
> and manageable through ReplicationAgent interface.
> This issue relates to the implementation of the response queue inside the 
> ReplicationAgent and making it accessible through ReplicationAgent.getQueue 
> API. The response queue is the queue where reverse replication on author 
> stores packages from publish.



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


[jira] [Updated] (SLING-3356) Expose the import queue for reverse replication through ReplicationAgent interface

2014-08-11 Thread Tommaso Teofili (JIRA)

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

Tommaso Teofili updated SLING-3356:
---

Component/s: (was: Extensions)
 Replication
 Labels:   (was: replication)

> Expose the import queue for reverse replication through ReplicationAgent 
> interface
> --
>
> Key: SLING-3356
> URL: https://issues.apache.org/jira/browse/SLING-3356
> Project: Sling
>  Issue Type: Improvement
>  Components: Replication
>Reporter: Marius Petria
>Assignee: Tommaso Teofili
> Attachments: SLING-3356.1.patch, SLING-3356.2.patch, 
> SLING-3356.3.patch, SLING-3356.patch
>
>
> The replication agent should have 3 main queues (the request queue, the 
> transport queue and the response queue). These queues should be accessible 
> and manageable through ReplicationAgent interface.
> This issue relates to the implementation of the response queue inside the 
> ReplicationAgent and making it accessible through ReplicationAgent.getQueue 
> API. The response queue is the queue where reverse replication on author 
> stores packages from publish.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (SLING-3356) Expose the import queue for reverse replication through ReplicationAgent interface

2014-02-20 Thread Tommaso Teofili (JIRA)

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

Tommaso Teofili updated SLING-3356:
---

Attachment: SLING-3356.3.patch

new version of Marius patch adapted to latest trunk

> Expose the import queue for reverse replication through ReplicationAgent 
> interface
> --
>
> Key: SLING-3356
> URL: https://issues.apache.org/jira/browse/SLING-3356
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Marius Petria
>Assignee: Tommaso Teofili
>  Labels: replication
> Attachments: SLING-3356.1.patch, SLING-3356.2.patch, 
> SLING-3356.3.patch, SLING-3356.patch
>
>
> The replication agent should have 3 main queues (the request queue, the 
> transport queue and the response queue). These queues should be accessible 
> and manageable through ReplicationAgent interface.
> This issue relates to the implementation of the response queue inside the 
> ReplicationAgent and making it accessible through ReplicationAgent.getQueue 
> API. The response queue is the queue where reverse replication on author 
> stores packages from publish.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Updated] (SLING-3356) Expose the import queue for reverse replication through ReplicationAgent interface

2014-02-11 Thread Marius Petria (JIRA)

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

Marius Petria updated SLING-3356:
-

Attachment: SLING-3356.2.patch

Adding jdocs to transport handler methods

> Expose the import queue for reverse replication through ReplicationAgent 
> interface
> --
>
> Key: SLING-3356
> URL: https://issues.apache.org/jira/browse/SLING-3356
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Marius Petria
>Assignee: Tommaso Teofili
>  Labels: replication
> Attachments: SLING-3356.1.patch, SLING-3356.2.patch, SLING-3356.patch
>
>
> The replication agent should have 3 main queues (the request queue, the 
> transport queue and the response queue). These queues should be accessible 
> and manageable through ReplicationAgent interface.
> This issue relates to the implementation of the response queue inside the 
> ReplicationAgent and making it accessible through ReplicationAgent.getQueue 
> API. The response queue is the queue where reverse replication on author 
> stores packages from publish.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Updated] (SLING-3356) Expose the import queue for reverse replication through ReplicationAgent interface

2014-02-10 Thread Marius Petria (JIRA)

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

Marius Petria updated SLING-3356:
-

Attachment: SLING-3356.1.patch

Fixing patch to be based on latest trunk

> Expose the import queue for reverse replication through ReplicationAgent 
> interface
> --
>
> Key: SLING-3356
> URL: https://issues.apache.org/jira/browse/SLING-3356
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Marius Petria
>Assignee: Tommaso Teofili
>  Labels: replication
> Attachments: SLING-3356.1.patch, SLING-3356.patch
>
>
> The replication agent should have 3 main queues (the request queue, the 
> transport queue and the response queue). These queues should be accessible 
> and manageable through ReplicationAgent interface.
> This issue relates to the implementation of the response queue inside the 
> ReplicationAgent and making it accessible through ReplicationAgent.getQueue 
> API. The response queue is the queue where reverse replication on author 
> stores packages from publish.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Updated] (SLING-3356) Expose the import queue for reverse replication through ReplicationAgent interface

2014-01-30 Thread Marius Petria (JIRA)

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

Marius Petria updated SLING-3356:
-

Attachment: SLING-3356.patch

- Moved packages from a transporthandler into the agent through a callback
- When a transport handler receives an answer it can call a queue processor and 
add the item to the response queue. The item will then be imported using the 
default packagebuilder.

Additional refactorings:
- made the queue providers, queue strategies and transport handler interfaces 
take the agentname as a parameter in order to allow them to be used by multiple 
agents. (they only take the name in order to minimize their exposure to the 
agent api)

- added a passive mode configuration to the agent to make it only store the 
packages, not auto process it.



> Expose the import queue for reverse replication through ReplicationAgent 
> interface
> --
>
> Key: SLING-3356
> URL: https://issues.apache.org/jira/browse/SLING-3356
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Marius Petria
>  Labels: replication
> Attachments: SLING-3356.patch
>
>
> The replication agent should have 3 main queues (the request queue, the 
> transport queue and the response queue). These queues should be accessible 
> and manageable through ReplicationAgent interface.
> This issue relates to the implementation of the response queue inside the 
> ReplicationAgent and making it accessible through ReplicationAgent.getQueue 
> API. The response queue is the queue where reverse replication on author 
> stores packages from publish.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)