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

ASF GitHub Bot commented on COUCHDB-3180:
-----------------------------------------

Github user nickva commented on the issue:

    https://github.com/apache/couchdb-chttpd/pull/144
  
    Alright, good points, agree. If it's worth doing, it's worth doing right.  
    
    Here is what I came with as first thing: 
    
    * Don't add a new application, it would be silly.
    
    * Stick it in config application. It seems like a configuration-y thing.
    
    * 3 new functions. API looks like
       - `config:features() -> [<<"feature1">>, <<"feature2">>, ...].`
       - `config:feature_enable(<<"feature1">>).`
       - `config:feature_disable(<<"feature2">>).`
    
    * Applications enable features and disable them. Then `chttpd` reads list 
of features from config and shows them in the welcome message.
    
    * Behind the scenes it is really just writing to config "[features]" 
section a bunch of booleans. With persistence set to `false`. 
    
    * Users can directly set "features" in the config file transparently.
    
    The advantage is it doesn't reinvent the world. Takes advantage of config 
server (so applications can monitor for changes and such if needed).
    
    ( Added same comment to https://issues.apache.org/jira/browse/COUCHDB-3180 )
    
    @rnewson I'll give this a try and see what it looks like


> Add ability to return a list of features in server's welcome message
> --------------------------------------------------------------------
>
>                 Key: COUCHDB-3180
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-3180
>             Project: CouchDB
>          Issue Type: New Feature
>            Reporter: Nick Vatamaniuc
>
> This could be used to let users discover quickly the availability of some API 
> or modes of operation.



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

Reply via email to