Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Wed, 4 Feb 2015 15:50:37 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: <JIRA.12771106.1422562166000.254720.1423065037322@Atlassian.JIRA>
In-Reply-To: <JIRA.12771106.1422562166000@Atlassian.JIRA>
References: <JIRA.12771106.1422562166000@Atlassian.JIRA>
 <JIRA.12771106.1422562166734@arcas>
Subject: [jira] [Commented] (COUCHDB-2561) Make config API consistent
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

ASF subversion and git services commented on COUCHDB-2561:
----------------------------------------------------------

Commit 4b102bf7de3b835cf82c81276deb3e4afbd942d9 in couchdb-chttpd's branch refs/heads/master from [~iilyak]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-chttpd.git;h=4b102bf ]

Update config_listener behaviuor

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)