couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Anderson (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (COUCHDB-216) Make couchdb adhere more to OTP guidelines
Date Mon, 23 Mar 2009 17:09:51 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Anderson reopened COUCHDB-216:
------------------------------------


It's generally agreed that we should make CouchDB more OTP-like. 

I'm not sure about the implementation or the timeline for doing it, but I think it's the best
path to auto-sharding.

> Make couchdb adhere more to OTP guidelines
> ------------------------------------------
>
>                 Key: COUCHDB-216
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-216
>             Project: CouchDB
>          Issue Type: Improvement
>            Reporter: Martin S
>         Attachments: 0001-add-couch_app-and-couch_sup.patch, 0001-Generate-the-modules-section-of-couch.app-via-the-Ma.patch,
0002-add-missing-registered-process-names.patch, 0003-make-couchdb-startup-script-use-couch.rel.-load-conf.patch
>
>
> CouchDB could adhere to otp standards in a better way. 
> Currently we have:
> - couch.app is not uptodate
> - couch_server.erl is an amalgam of 2 behaviours, which is considered being "not good".
> From my beginner's perception of OTP, it seems CouchDB is not treated as a running application
when it is actually running. E.g. appmon doesn't show the application once CouchDB is started.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message