ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Offermans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACE-382) Implement a FeedbackControl service.
Date Thu, 22 Aug 2013 09:06:51 GMT

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

Marcel Offermans commented on ACE-382:
--------------------------------------

Regarding the three bullets you propose:

* I don't think we should enforce that channels that the agent logs must be available on the
server or vice versa. I agree they should match, but if someone wants to configure them differently,
he should be able to do so. In theory, different channels could go to different servers, so
the current "negotiation" between the two parties ensures that only feedback is exchanged
that is wanted by the receiving party.
* Agreed, that's a configuration aspect.
* Agreed, if you want a different strategy, you can implement it yourself.

The API looks fine to me.
                
> Implement a FeedbackControl service.
> ------------------------------------
>
>                 Key: ACE-382
>                 URL: https://issues.apache.org/jira/browse/ACE-382
>             Project: ACE
>          Issue Type: Task
>          Components: Log, Management Agent
>            Reporter: Marcel Offermans
>
> On the target, the management should expose a FeedbackControl service API that allows
consumers to control every aspect of the feedback mechanism.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message