couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Russell Branca (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-2079) Re-enable configurable HTTP handlers
Date Thu, 20 Feb 2014 23:13:24 GMT

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

Russell Branca commented on COUCHDB-2079:
-----------------------------------------

+1 to having an empty http layer that allows app to plug into it.

I think it would also be interesting to update the handler functions to be less dependent
on http, basically keep http isolated to chttpd, and have all the other things return erlang
data structures. Basically make http a particular interface type, allowing for alternative
interfaces or direct access.

> Re-enable configurable HTTP handlers
> ------------------------------------
>
>                 Key: COUCHDB-2079
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2079
>             Project: CouchDB
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: BigCouch
>            Reporter: Paul Joseph Davis
>              Labels: release
>
> chttpd hard codes HTTP handlers rather than lists them in the config files. We'll need
to revert this change. Though given how some apps (couch_mrview, etc) have their own handlers
we should consider making this configurable at the app-level instead of the ini level in CouchDB.
> I have a few ideas on this, mostly by removing all handler code from chttpd and friends.
The HTTPd app would then just start empty servers with no handlers and each app would have
a supervision tree process that would be responsible for registering handlers.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message