[
https://issues.apache.org/jira/browse/COUCHDB-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14305316#comment-14305316
]
ASF subversion and git services commented on COUCHDB-2561:
----------------------------------------------------------
Commit aa36a185ead7c0232b614cac5abd798fa2d55747 in couchdb-couch's branch
refs/heads/master from [~kxepal]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-couch.git;h=aa36a18 ]
Merge remote-tracking branch 'iilyak/2561-make-config-API-consistent'
This closes #34
COUCHDB-2561
> Make config API consistent
> --------------------------
>
> Key: COUCHDB-2561
> URL: https://issues.apache.org/jira/browse/COUCHDB-2561
> Project: CouchDB
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Database Core
> Reporter: ILYA
> Assignee: ILYA
>
> There are 2 problems with API which need to be fixed.
> 1) Mix of message driven and callback driven
> API for config_listener is hard to use.
> In particular there is a gen_event_EXIT
> message which is sent to the process which called config:listen_for_changes.
> This makes API unsuitable for use in the context of a supervisor. Since
> supervisors do not support handling of arbitrary messages. This message also
> causing problems for test suite.
> This message could be substituted with
> a call to Module:handle_config_stop(Pid, Reason, State).
> 2) Since for section, key, value we only support lists but not arbitrary
> terms. More strick guards are needed to make sure the caller of the API fails
> with badarg
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
