[jira] [Commented] (COUCHDB-2561) Make config API consistent

["ILYA (JIRA)" <ji...@apache.org>]

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

ILYA commented on COUCHDB-2561:
-------------------------------

https://github.com/apache/couchdb-config/pull/2
https://github.com/apache/couchdb-chttpd/pull/21
https://github.com/apache/couchdb-couch/pull/34
https://github.com/apache/couchdb-couch-index/pull/4
https://github.com/apache/couchdb-couch-replicator/pull/7
https://github.com/apache/couchdb-mem3/pull/5
https://github.com/apache/couchdb-couch-event/pull/1
https://github.com/apache/couchdb-global-changes/pull/2

This also depends on https://github.com/apache/couchdb-couch-mrview/pull/15

> 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)